[
http://jira.codehaus.org/browse/MSITE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233145#action_233145
]
Dennis Lundberg commented on MSITE-497:
---------------------------------------
It's the Javadoc Plugin that is triggering the compile phase in the first
place, see MJAVADOC-281. This works fine as long as it is not an aggregator
build. The attached example is a multi module build which automatically
triggers the AggregatorJavadocReport, instead of the normal JavadocReport that
is used for a single module build. There doesn't seem to be a way to *not* use
aggregated Javadocs in a multi module build any longer. This used to work in
previous versions of the Javadoc Plugin.
The AggregatorJavadocReport has the @aggregator annotation, which is what I
think is triggering the forking. See this thread for more issues with the
@aggregator annotation
http://maven.40175.n5.nabble.com/aggregator-mojo-annotation-td207938.html
and this wiki page for some documentation on it
http://docs.codehaus.org/display/MAVEN/Aggregator+Plugins
The AbstractJavadocMojo has {...@requiresdependencyresolution compile}} which
according to the docs means that _"the core will resolve the dependencies for
all projects in the reactor and not just for the current project"_
The JavadocReport has {...@execute phase="generate-sources"}} which triggers
forking
The AggregatorJavadocReport has {...@aggregator}}
The above 3 classes are in order of inheritance.
To me this sounds like an issue with dependency resolution in Maven core.
> Dependencies not included classpath for multi-level projects when forking
> reporting
> -----------------------------------------------------------------------------------
>
> Key: MSITE-497
> URL: http://jira.codehaus.org/browse/MSITE-497
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 3.0-beta-1
> Environment: Maven 3.0-beta-2
> MacOS 10.6.4/Windows XP SP2 (or possibly SP3)
> Mac Java 1.6.0_20/SUN JDK 1.6.0_15
> Reporter: Anders Hammar
> Priority: Critical
> Attachments: mvn3site-bug.zip, mvn_site_output.txt
>
>
> Executing "mvn site" on a multi-level project, where it hasn't been compiled
> first, makes the build fail because the dependencies can't be found (aren't
> included on the classpath).
> The attached test projects shows this. If run with Maven 2.2.1 it works fine,
> with Maven 3.0-beta-2 it fails. I'm also attaching a debug output of this.
> To recreate the issue on the project:
> mvn clean
> mvn site
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
