Thanks for the suggestions guys, but I eventually did figure out my problem after much suffering. It looks to me like the javadoc plugin has a bug where it gives very misleading error messages. The source of all my errors seems to have been an invalid package.html file somewhere in one of my modules. This apparently caused the javadoc plugin to generate lots of bogus error messages about not being able to find dependent classes.
I opened a JIRA issue: http://jira.codehaus.org/browse/MJAVADOC-102. -Adam On 11/19/06, diroussel <[EMAIL PROTECTED]> wrote:
Do your module names match the directory names which match the artifact ids? Adam Lally-2 wrote: > > On 11/16/06, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: >> Adam- >> >> I've experienced that as well. My workaround is to first run "mvn >> install" and then "mvn javadoc:javadoc", and it seems to work. >> >> > > Thanks, that got my simple test case with just one module to work. My > multimodule build is still failing with missing dependencies, though. > mvn install runs fine, but mvn javadoc:javadoc gives errors. :( > > I will try to simplify my build and see when it stops breaking. But > in the meantime if anyone can enlighten me as to reasons why mvn > install might work while mvn javadoc:javadoc doesn't, I'd appreciate > it. > > -Adam > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Can%27t-get-javadoc-plugin-to-work-for-multimodule-project-tf2647522s177.html#a7429647 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
