[
http://jira.codehaus.org/browse/MNG-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-3281.
----------------------------------
Assignee: Benjamin Bentmann (was: Jason van Zyl)
Resolution: Fixed
Fix Version/s: (was: 3.0-alpha-4)
3.0-alpha-3
Fixed in [r815761|http://svn.apache.org/viewvc?view=rev&revision=815761].
Just to mention it, we can't completely cut off plugins from the extensions
because plugins can inspect the execution plan or create&resolve artifacts.
Those tasks require access to lifecycle mappings and artifact handlers, both
contributed by extensions.
We now have the following parent-child chain of class realms on trunk: core
realm -> project realm -> plugin realm. The project realm is only present if
the project actually declares any extensions, otherwise the plugin realm is a
direct child of the core realm.
The project realm aggregates all JARs from its build extensions so there's the
potential for conflicts between extensions. For the moment, this should work
well enough, more sophisticated class loader setups likely require more
metadata in the extension JARs, e.g. what should be exported/shared and what is
private impl.
> Revisit backwards compat of extensions (IT 0114)
> ------------------------------------------------
>
> Key: MNG-3281
> URL: http://jira.codehaus.org/browse/MNG-3281
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 3.0-alpha-1
> Reporter: Brett Porter
> Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> currently, it 0114 doesn't pass due to the removal of extension support
> we need to either:
> - restore some form of backwards compat by loading the extension into the
> expected place
> - provide a graceful failure instead
--
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
