[ http://jira.codehaus.org/browse/MNG-214?page=all ]
John Casey resolved MNG-214:
----------------------------
Resolution: Fixed
fixed by removing artifact container and replacing with nested containers
per-plugin
> plugin parameters instantiated from wrong classloader
> -----------------------------------------------------
>
> Key: MNG-214
> URL: http://jira.codehaus.org/browse/MNG-214
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-alpha-3
>
>
> example: can't currently build maven-assemble-plugin as the /build/ uses the
> modello plugin, but the plugin-plugin is loaded because of the build type.
> in populating the modello plugin, #component.org.codehaus.modello.ModelloCore
> is looked up by role. The lookup finds the class from the maven-plugin-plugin
> classloader, as it was the first classloader to be registered with plexus.
> However, the modello plugin is executed in the modello-plugin classloader -
> classcastexception results.
> What needs to happen is that when constructing the arguments for the modello
> plugin, all lookups must take place inside the modello classloader (how to
> feed this down to plexus, I don't know).
> The offending line where the wrong classloader is discovered is
> JavaComponentFactory:24:
> ClassRealm componentClassRealm = container.getComponentRealm(
> componentDescriptor.getComponentKey() );
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
