You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/12/31 07:20:10 UTC
[jira] Reopened: (MNG-2228) Classloader problem loading jars from
build extensions
[ http://jira.codehaus.org/browse/MNG-2228?page=all ]
Brett Porter reopened MNG-2228:
-------------------------------
this caused some problems with the release plugin because jdom was in the root container (via wagon-webdav), but jaxen was not (because it is optional, so it was not caught by the resolution I added).
I have an alternate solution putting extensions in a child container like plugins which is working. I will clean up and commit tomorrow.
This could be reviewed and handled differently for trunk given the changes to plexus and classworlds. I'll examine that separately.
> Classloader problem loading jars from build extensions
> ------------------------------------------------------
>
> Key: MNG-2228
> URL: http://jira.codehaus.org/browse/MNG-2228
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Carlos Sanchez
> Assigned To: Brett Porter
> Priority: Blocker
> Fix For: 2.0.5
>
> Attachments: MNG-2228.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