You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/03/21 17:15:46 UTC
[jira] Reopened: (MNG-3473) site generation with 2.0.9 and
plugin:report is broken
[ http://jira.codehaus.org/browse/MNG-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey reopened MNG-3473:
-----------------------------
The issue with the plugin plugin isn't the LinkedHashSet...it's incorrect ordering of dependencies in the plugin's POM, and a change in the artifact-resolution code that uses an ordered set now where it didn't used to.
I've verified that the ordering of artifacts resolved for the same plugin POM is different between 2.0.8 and the 2.0.9 code, where the 2.0.9 resolution order is actually correct...the plugin POM specifies dependencies on maven-reporting-impl 2.0.4 and doxia-site-renderer 1.0-alpha-10 IN THAT ORDER. This means that it resolves:
# maven-reporting-impl 2.0.4 -> doxia-core 1.0-alpha-7
# doxia-site-renderer 1.0-alpha-10 -> doxia-core 1.0-alpha-10
and, since it sees -alpha-7 of doxia-core FIRST (it's at the same transitivity level as the other doxia-core dependency), -alpha-7 wins. This is correct according to the rules implemented in the ArtifactCollector. Previously, I think it was just dumb luck that it worked using a bad ordering algorithm (or, more precisely, no ordering algorithm).
> site generation with 2.0.9 and plugin:report is broken
> ------------------------------------------------------
>
> Key: MNG-3473
> URL: http://jira.codehaus.org/browse/MNG-3473
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.9
> Reporter: Brian Fox
> Assignee: John Casey
> Fix For: 2.0.9
>
>
> Generating a site that works in 2.0.8 breaks in 2.0.9 with an exception: Caused by: java.lang.NoClassDefFoundError: org/apache/maven/doxia/module/site/manager/SiteModuleNotFoundException
> There is already a committed IT for this. It may be related to issues with MPLUGIN-104, however in this case the 2.4 version of the plugin does work in 2.0.8 so we need to investigate it in the core as well.
--
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