[
https://jira.codehaus.org/browse/MSITE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292744#comment-292744
]
Benson Margulies commented on MSITE-171:
----------------------------------------
I have some evidence that this isn't a site plugin bug in the usual sense.
Rather, it seems to be related (for me) to MNG-2277.
The comment in LifecycleDependencyResolver seems all too relevant. I hit this
problem only when I use the aggregating javadoc report, with the backtrace
below.
MNG-2277, the check below compensates for our bad plugin support where we ended
up with aggregator
plugins that require dependency resolution although they usually run in phases
of the build where project
artifacts haven't been assembled yet. The prime example of this is "mvn
release:prepare".
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Site plugin uses plain dependencies for reactor projects instead of results
> of earlier modules
> ----------------------------------------------------------------------------------------------
>
> Key: MSITE-171
> URL: https://jira.codehaus.org/browse/MSITE-171
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: multi module
> Affects Versions: 2.0-beta-5
> Environment: Win XP, Linux
> Reporter: Alex Rau
> Attachments: install_site_runs.log, site_fails.log,
> subsequent_site_runs.log
>
>
> When creating a multi-module site the site plugin uses dependencies from
> related modules from the repository instead of using artifacts from the same
> execution.
> That causes inconsistent reports on the sites. An example:
> Project A has modules B and C defined. B is build first and a site for
> project B is created. Then project C is build using a dependency either from
> the local or remote repository. Therefore the site contains results which
> rely on a build with an "out-dated" artifact used as dependency. This leads
> to plainly wrong results when examining surefire-reports as Project C should
> have been build with the (current) artifact of project B (taken from the same
> execution of the site plugin).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
