Opened 7 years ago
Closed 7 years ago
#15886 closed enhancement (fixed)
javadoc and sources for plugins
Reported by: | stoecker | Owned by: | Don-vip |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin | Version: | |
Keywords: | javadoc artifact nexus maven gradle | Cc: |
Description
You added a new javadoc target and eventbus plugin. The sources and javadoc jar file may be generated, although I don't know why this should be generated as jar, but they should never go into dist directory, as these are no valid plugins!
Attachments (0)
Change History (4)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Already committing the binaries to svn is not really the best solution. Adding more to that is not a good idea. It's not a problem to create them, but they should not added to SVN.
comment:4 by , 7 years ago
Keywords: | javadoc artifact nexus maven gradle added |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Fixed. Jenkins now directly generates the source/javadoc artifacts and pushes them to Nexus.
*-sources.jar
and*-javadoc.jar
is the standard packaging format for Maven/Gradle artifacts. This commit aims to ease development for plugin authors using these build tools, in order to publish them to our nexus instance. In the long term, we could even publish directly to Maven Central.I can exclude these special jars from being processed by our cron job, like what is already done when a plugin includes a library: