[ http://jira.codehaus.org/browse/MNG-2225?page=all ]
John Casey updated MNG-2225:
----------------------------
Fix Version: (was: 2.0.5)
2.1
this will mean changing the way we build the list of artifacts to filter out of
the resolution process (because they're already in the core classloader). We'll
have to find a dynamic way to manage that, which might mean installing an
internal local repository for Maven itself, so we can build up an index of
artifacts that are in there.
Any way we go, it represents new design to solve this problem. I think it would
be better to do this in the context of design for customizing maven instances,
currently planned for 2.1.
> Classloader problem when adding jars to M2_HOME
> -----------------------------------------------
>
> Key: MNG-2225
> URL: http://jira.codehaus.org/browse/MNG-2225
> Project: Maven 2
> Type: Bug
> Components: Dependencies
> Versions: 2.0.4
> Reporter: Carlos Sanchez
> Priority: Critical
> Fix For: 2.1
> Attachments: testwagonscm.tgz
>
>
> Added these jars to M2_HOME/custom to allow using scm based remote repos
> http://www.ibiblio.org/maven2/org/apache/maven/scm/maven-scm-api/1.0-beta-2/maven-scm-api-1.0-beta-2.jar
> http://www.ibiblio.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.0-beta-2/maven-scm-manager-plexus-1.0-beta-2.jar
> http://www.ibiblio.org/maven2/org/apache/maven/scm/maven-scm-provider-svn/1.0-beta-2/maven-scm-provider-svn-1.0-beta-2.jar
> http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/wagon/wagon-scm/1.0-alpha-7-SNAPSHOT/wagon-scm-1.0-alpha-7-20060308.183410-3.jar
> bin/m2.conf
> main is org.apache.maven.cli.MavenCli from plexus.core.maven
> set maven.home default ${user.home}/m2
> [plexus.core]
> load ${maven.home}/core/*.jar
> [plexus.core.maven]
> load ${maven.home}/custom/*.jar
> load ${maven.home}/lib/*.jar
> 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.
--
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
