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
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
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
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
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
I stripped out all modules and run it again. It still complains as shown
below:
D:\maven1\testmvn javadoc:jar -Daggregate=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'javadoc'.
WAGON_VERSION: 1.0-beta-2
[INFO]
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
