On 14 June 2012 19:02, Ancoron Luciferis <[email protected]> wrote: > On 06/14/2012 05:51 PM, David Bosschaert wrote: >> >> You're right - maven insists on javadoc. I think this is specific to the >> manual upload mechanism [1] (which we have to use here) as there are >> lots of other released maven artifacts that don't have javadoc. >> >> Not sure what to do here. I think that more things will work if you put >> the javadoc at the root, even though it might cause broken links, so I'm >> inclined to go that way. Most IDEs can extract the javadoc out the >> source code anyway so we don't really need it - its just to keep the >> maven upload process happy... >> >> Cheers, >> >> David >> >> [1] >> >> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository > > > It's not a direct requirement of Maven but rather a policy of the central > repository. > > Anyway, I just tested with NetBeans 7.x and to my surprise everything works > just fine, the binaries, the JavaDoc and the sources. So other current IDE's > should be fine with it, too.
Hi Ancoron, See my other post, IntelliJ isn't fine with it... David _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
