You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/30 03:27:55 UTC
[jira] Commented: (MNG-2771) Provide a means of loading custom
substitute components instead of default Maven components
[ http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204494#action_204494 ]
Jason van Zyl commented on MNG-2771:
------------------------------------
This can be done by dropping in components, or using the new extension mechanism where plugins can add core components.
> 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 & 3
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.4
> Reporter: John Casey
> Assignee: Igor Fedorenko
> Fix For: 3.x
>
>
> 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