A small correction: The @options file does contain the dependencies of the first A module (A1), but misses those of all other A modules (for example A2).
We use the following directory layout: A-parent/pom.xml A1/pom.xml A2/pom.xml B/B-parent/pom.xml B/B1/pom.xml B/B2/pom.xml Hope this helps, Holger Holger Brands wrote: > > Hi, > > we get the same exception trace using Maven 2.2.1 and after upgrading > to javadoc plugin 2.6. Now we use the aggregate goal in a report set > instead of the aggregate config parameter. > > We hava a mulit-module build with two layers of aggregation: > > A-parent > - A1 > - A2 > - B-parent > - B1 > - B2 > > In both parents the aggregate javadoc reportset is defined. > When executing "mvn install site" in the top-level parent "A-parent" > the exception occurs. > (Removing the aggregate javadoc report set from B-parent does not help.) > It seems to me that in this case the generated @options file does not > contain > the dependencies of the A1 and A2 modules, but only those of > modules B1 and B2. > > Can somone confirm this behaviour? > Is this the cause of the exception? > > Thanks, > Holger > > > Benoit DECHERF-3 wrote: >> >> Hi, >> >> In my project, when I execute mvn javadoc:javadoc, The javadoc generation >> works. >> >> But It fails when I execute mvn site, it fails: >> ------------------------------- >> [INFO] Generating "JavaDocs" report. >> Loading source files for package >> com.xxxxx.euromarketplace.search.cleaner... >> Constructing Javadoc information... >> Standard Doclet version 1.6.0_16 >> Building tree for all the packages and classes... >> 34 warnings >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Error during page generation >> >> Embedded error: Error rendering Maven report: Exit code: 1 - >> /home/decherfb/tmp/searchCleaner/src/java/com/xxxx/euromarketplace/search/cleaner/Configuration.java:13: >> package com.xxxx.processframework.services does not exist >> import com.xxxx.processframework.services.ServiceException; >> >> .... >> >> java.lang.NullPointerException >> at com.sun.tools.javadoc.TypeMaker.getType(TypeMaker.java:67) >> at com.sun.tools.javadoc.TypeMaker.getType(TypeMaker.java:29) >> at >> com.sun.tools.javadoc.ClassDocImpl.superclassType(ClassDocImpl.java:441) >> .... >> at com.sun.tools.javadoc.Main.main(Main.java:31) >> >> Command line was:/usr/java/jdk1.6.0_16/jre/../bin/javadoc @options >> @packages >> .... >> -------------------------------------------------------------- >> the @options doesn't have a correct classpath : the missing class is in >> an >> artifact A1.jar. >> >> In the pom, I have the dependency on A1.jar and A1-script.tgz (In this >> order). >> >> If I inverse the order of these dependencies, the site generation works! >> Do you have an idea on this bug ? >> >> Thanks, >> Benoit >> >> > > -- View this message in context: http://www.nabble.com/javadoc-generation-fails-only-during-site-generation-tp25508297p25641699.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
