IMO, it's an issue [1]. Because dependencies declared in child modules are not adding in the javadoc cli which is launched in the root module. Moving dependencies in the root pom works but it's not what I want to do. I need to declare dependencies only where I need it (moving to root propagate to all childs). You can declare a new profile in your root pom which include all dependencies and try the aggregate javadocs with activating this. Not tested but certainly works ?
- Olivier [1] http://jira.codehaus.org/browse/MJAVADOC-72 -----Message d'origine----- De : Daun DeFrance [mailto:[EMAIL PROTECTED] Envoyé : lundi 22 mai 2006 17:51 À : Maven Users List Objet : RE: [m2.0.4] Javadoc aggregate problems with multiple modules projects Stefan, I am having the same problem which I posted last Friday. Removing the aggregate=true flag allows the javadoc to run successfully. I am at a loss and haven't seen any responses indicating what the problem is. Sorry I couldn't be more help, but if you find a solution, please post it to the group. Thanks, Daun -----Original Message----- From: Stefan Kanev [mailto:[EMAIL PROTECTED] Sent: Monday, May 22, 2006 9:31 AM To: users@maven.apache.org Subject: [m2.0.4] Javadoc aggregate problems with multiple modules projects Hi all. Setting aggregate to true for the javadoc plugin doesn't seem to work for me, in a multiple-module build. I won't paste error message, because they are just too large, but it tells me that it can't find some classes (from external dependencies) that it succesfully finds when I'm building the project. After that, I get a lot of java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl exceptions and duh. The problem disappears when I move those dependencies from the <dependencyManagement> to the <dependencies> tag in the code. It leads me to think, that the javadoc plugin ignores the dependencies in <dependencyManagement>. I read somewhere (I don't remember where) that this is currently fixed in the CVS for maven-javadoc-plugin, but a fresh checkout produces the same error. Ideas, anyone? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, any attachments and the information contained therein ("this message") are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. -------------------------------------------------------------------------------------------------------------- Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après "le message" ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
