On Tue, 8 Jan 2013 14:19:14 +0000 Stephen Connolly <[email protected]> wrote:
> I haven't looked at your project but I have a suspicion as to what is > going on. > > By default the javadoc.jar is not generated by a default build, so as > a result there is no javadoc.jar in the reactor and hence there is a > search of the local and remote repositories... but since these do not > have the javadoc.jar attached either, you get the complaint. > > When you run a release using the release plugin, the standard release > profile adds in executions for source:jar and javadoc:jar which will > result in the artifacts being available in the reactor and hence both > deployed to the remote repository and available for aggregation. > > Please try adding the following to your maven command > > -P+release > > if the build works with that added to the command line, then my > theory is correct Hi, thanks for the quick reply. Unfortunately, adding the flag didn't make any difference. I should mention that I'm not actually using the release plugin (due to having an unsupported SCM). It does cause a warning before the existing javadoc error: [WARNING] The requested profile "release" could not be activated because it does not exist. M --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
