You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/07/02 21:40:10 UTC
[jira] (MNG-2771) Provide a means of loading custom substitute
components instead of default Maven components
[ https://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov updated MNG-2771:
--------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
3.0
> Provide a means of loading custom substitute components instead of default Maven components
> -------------------------------------------------------------------------------------------
>
> Key: MNG-2771
> URL: https://jira.codehaus.org/browse/MNG-2771
> Project: Maven
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.4
> Reporter: John Casey
> Assignee: Igor Fedorenko
> Fix For: 3.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)