[ http://jira.codehaus.org/browse/MNG-2228?page=comments#action_64232 ]
Carlos Sanchez commented on MNG-2228: ------------------------------------- This breaks generation of site when wagon-scm is in the build extensions, eg. to deploy the site to svn or cvs for Collabnet (dev.java.net) When running site Maven tries always to instantiate projec-info-report mojos *before* checking in the pom for "exclude default reports" option. The only way to generate the site was install the project-info-report plugin after removing the class ScmReport. It has to go under the same groupId, org.apache.maven.plugins, which makes it a real hack > Classloader problem loading jars from build extensions > ------------------------------------------------------ > > Key: MNG-2228 > URL: http://jira.codehaus.org/browse/MNG-2228 > Project: Maven 2 > Type: Bug > Components: Dependencies > Versions: 2.0.4 > Reporter: Carlos Sanchez > Priority: Blocker > Attachments: testwagonscm-extensions.tgz > > > When running "mvn install" and "mvn testwagonscm:test" in the attached test > case you get a ClassCastException although the Class to assign to and the > assigned one are the same. The problem seems to be that they come from > different classloaders. This problem makes the project-info-report:scm goal > fail. > Same as MNG-2225, but using build extensions instead of jars in M2_HOME -- 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