You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was recently working on integrating dokka into an android library, and despite being able to apply the plugin with no issues, sources/javadoc jars were strangely not getting generated. Finally after updating to 0.9.18, I suddenly would get a crash looking up a configuration that didn't exist. When tracing down this code, I noticed that it was emanating from the non-android plugin. This made me realize that the artifact used in my project was wrong, and finally resolved my jar generation after switching.
Is there a need for two artifacts? Especially when seemingly applying either plugin can be applied from the wrong artifact. https://github.com/square/sqldelight did something similar in the beginning and unified their plugin after the confusion it caused, and I'd be interested to know if there's a technical reason dokka has to have them separate.
The text was updated successfully, but these errors were encountered:
I was recently working on integrating dokka into an android library, and despite being able to apply the plugin with no issues, sources/javadoc jars were strangely not getting generated. Finally after updating to 0.9.18, I suddenly would get a crash looking up a configuration that didn't exist. When tracing down this code, I noticed that it was emanating from the non-android plugin. This made me realize that the artifact used in my project was wrong, and finally resolved my jar generation after switching.
Is there a need for two artifacts? Especially when seemingly applying either plugin can be applied from the wrong artifact. https://github.com/square/sqldelight did something similar in the beginning and unified their plugin after the confusion it caused, and I'd be interested to know if there's a technical reason dokka has to have them separate.
The text was updated successfully, but these errors were encountered: