I understand that. Unfortunetaly, we have such need for the customers on the legacy ground.
If it's not recommended, how come maven javadoc plug-in page advocates this usage. Please see: http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html On 2/12/08, VUB Stefan Seidel <[EMAIL PROTECTED]> wrote: > > Hi Ryan, > > the thing is: in maven philosophy, it does not make sense to create an > aggregate javadoc jar. A javadoc jar contains the sources for _one_ > artifact, so that for that specific artifact an IDE could for example > download this javadoc jar in order to have the javadoc available for all > the classes in this artifact. I understand that you want all the > aggregated javadoc in one file, but to do that you cannot use standard > maven procedures. Just package the aggregate javadoc yourself. > > HTH, > > Stefan > > Ryan H. wrote: > > Has anyone successfully used "mvn javadoc:jar -Daggregate=true" for > multiple > > projects? > > > > Here is the directory structure for my multiple projects: > > > > Project > > |-- pom.xml > > |-- Module1 > > | `-- pom.xml > > |-- Module2 > > | `-- pom.xml > > `-- Module3 > > `-- pom.xml > > > > Now, when I run "mvn javadoc:jar -Daggregate=true" under "Project", it > > always throws me this info without doing anything: > > > > *[INFO] Not executing Javadoc as the project is not a Java > classpath-capable > > package* > > > > I downloaded the source code of maven-javadoc-plugin and added the debug > > statement before the above line is printed in this block of code > snippet: > > > > > > ArtifactHandler artifactHandler = project > > .getArtifact().getArtifactHandler(); > > > > *if* ( !"java".equals( artifactHandler.getLanguage() ) ) > > > > { > > > > getLog().info("problematic artifact is: " + project.getArtifactId() + ", > > language: " + artifactHandler.getLanguage()); > > > > getLog().info( "Not executing Javadoc as the project is not a Java > > classpath-capable package" ); > > > > } > > > > And it turned out to be complaining about "Project", whose "packing > type" is > > "pom" and "language" is "none": > > > > [INFO] [javadoc:jar] > > [INFO] problematic artifact is: Project, language: none > > [INFO] Not executing Javadoc as the project is not a Java > classpath-capable > > package > > > > > > Am I missing something? Anyone has a clue? > > > > Thanks > > > > On 1/29/08, Ryan H. <[EMAIL PROTECTED]> wrote: > > > >> I stripped out all modules and run it again. It still complains as > shown > >> below: > >> > >> D:\maven1\test>mvn javadoc:jar -Daggregate=true > >> [INFO] Scanning for projects... > >> [INFO] Searching repository for plugin with prefix: 'javadoc'. > >> WAGON_VERSION: 1.0-beta-2 > >> [INFO] > >> > ---------------------------------------------------------------------------- > >> [INFO] Building Foundations POM > >> [INFO] task-segment: [javadoc:jar] (aggregator-style) > >> [INFO] > >> > ---------------------------------------------------------------------------- > >> [INFO] Preparing javadoc:jar > >> [INFO] > >> > ---------------------------------------------------------------------------- > >> [INFO] Building MyProjects POM > >> [INFO] > >> > ---------------------------------------------------------------------------- > >> [INFO] No goals needed for project - skipping > >> *[INFO] [javadoc:jar] > >> [INFO] Not executing Javadoc as the project is not a Java > >> classpath-capable package > >> *[INFO] > >> > ------------------------------------------------------------------------ > >> [INFO] BUILD SUCCESSFUL > >> [INFO] > >> > ------------------------------------------------------------------------ > >> [INFO] Total time: 1 second > >> [INFO] Finished at: Tue Jan 29 17:42:20 PST 2008 > >> [INFO] Final Memory: 7M/508M > >> [INFO] > >> > ------------------------------------------------------------------------ > >> > >> > >> > >> On 1/29/08, Ryan H. <[EMAIL PROTECTED]> wrote: > >>> Hi Vincent, > >>> > >>> I invoke javadoc:jar from my top level POM whose package type is > "pom". > >>> All modules included are java projects and their packaging types are > "jar" > >>> across the board ... > >>> > >>> > >>> On 1/29/08, Vincent Siveton <[EMAIL PROTECTED]> wrote: > >>>> Hi Ryan, > >>>> > >>>> What is your packaging type of your project (or subprojects)? It > seems > >>>> it is not a java one. > >>>> > >>>> Cheers, > >>>> > >>>> Vincent > >>>> > >>>> 2008/1/29, Ryan H. <[EMAIL PROTECTED]>: > >>>>> Hello, > >>>>> > >>>>> Anyone knows what this javadoc:jar complains about? I'm able to run > >>>>> javadoc:javadoc in "aggregate" mode (ie. generate only one report > >>>> for > >>>>> all multiple projects). However, when I run javadoc:jar, it starts > >>>>> complaining it ... > >>>>> > >>>>> [INFO] [javadoc:jar] > >>>>> [INFO] Not executing Javadoc as the project is not a Java > >>>> classpath-capable > >>>>> package > >>>>> > >>>>> Thanks > >>>>> Ryan > >>>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > > > > -- > best regards, > > Stefan Seidel > software developer > ________________________ > VUB Printmedia GmbH > Chopinstraße 4 > D-04103 Leipzig > Germany > tel. +49 (341) 9 60 50 07 > fax. +49 (341) 9 60 50 92 > mail. [EMAIL PROTECTED] > web. www.vub.de > > HRB Köln 24015 > UStID DE 122 649 251 > GF Dr. Achim Preuss Neudorf, > Dr. Christian Preuss Neudorf > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
