You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2015/09/10 08:12:46 UTC

[jira] [Comment Edited] (MNG-5774) Provide an extension point to provide alternate CLI configuration mechanism

    [ https://issues.apache.org/jira/browse/MNG-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14420114#comment-14420114 ] 

Hervé Boutemy edited comment on MNG-5774 at 9/10/15 6:12 AM:
-------------------------------------------------------------

Change made on [7997634209cf2e666aa94ece24e089da179d8aa3|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=7997634209cf2e666aa94ece24e089da179d8aa3]


was (Author: jvanzyl):
Change made on 7997634209cf2e666aa94ece24e089da179d8aa3

> Provide an extension point to provide alternate CLI configuration mechanism
> ---------------------------------------------------------------------------
>
>                 Key: MNG-5774
>                 URL: https://issues.apache.org/jira/browse/MNG-5774
>             Project: Maven
>          Issue Type: New Feature
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>             Fix For: 3.3.1
>
>
> Currently the only way to configure an execution session is the settings.xml file mechanism. In essence the code currently works to read the settings.xml file(s) and stuffs a bunch of values in the MavenExecutionRequest. It should be possible to easily use different sources of values and use different logic to populate those values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)