[
http://jira.codehaus.org/browse/MNG-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109545
]
John Casey commented on MNG-3181:
---------------------------------
If the problem is pollution from extensions, can't we find a way to define
standard extension points, then load extensions into separate realms and only
put imports from those realms into the main realm for implementations of the
standard extensions points?
This seems a lot less severe than altering the entire classloading method,
which could have severe ramifications for things trying to share project
information, for instance...
> JDOM artifact filtering is causing problems
> -------------------------------------------
>
> Key: MNG-3181
> URL: http://jira.codehaus.org/browse/MNG-3181
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 2.1-alpha-1
>
>
> For example in the release plug that requires JDOM which uses Jaxen. We are
> cutting off resolution of Jaxen so the release plugin fails. Anything that
> requires Jaxen via JDOM will 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
