[
http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98192
]
Kenney Westerhof commented on MNG-2771:
---------------------------------------
I don't think this'll be available in 2.0.x, as it uses some heavily refactored
code in 2.1.
It should now all work in 2.1-snapshot; the extensions is not mentioned in the
m2.conf because
it needs special treatment. The embedder/cli will check if M2_HOME/extensions
exists and process
it's contents during startup.
The reason it's not in m2.conf is that m2.conf is for the classworlds booter
and contains no maven
specific configuration whatsoever. The extensions are maven specific. m2.conf
should actually
be called 'classworlds.conf' since it's unrelated to maven itself.
> 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
