[
http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106256
]
Jason van Zyl commented on MNG-2771:
------------------------------------
Only method 1) works and that was the only thing that was planned at the time
but using extensions (at first blush) would probably be fine as you want to use
them globally across all your builds.
> Provide a means of loading custom substitute components instead of default
> Maven components
> -------------------------------------------------------------------------------------------
>
> Key: MNG-2771
> URL: http://jira.codehaus.org/browse/MNG-2771
> Project: Maven 2
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.4
> Reporter: John Casey
> Assignee: Kenney Westerhof
> Fix For: 2.1-alpha-1
>
>
> At times, it is necessary to use different mechanisms for resolving
> artifacts, building projects, etc. Since Maven is built on component-oriented
> technology, it should be possible to substitute the component implementation
> used for these tasks. Yet this is currently impossible.
> We need a mechanism for specifying, resolving, loading, and using custom
> components during the build process.
--
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
