You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/06/04 07:04:40 UTC
[jira] [Commented] (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=14572151#comment-14572151 ]
Hudson commented on MNG-5774:
-----------------------------
SUCCESS: Integrated in maven-3.x #1081 (See [https://builds.apache.org/job/maven-3.x/1081/])
MNG-5774 restored MavenCli user/global settings location contants (ifedorenko: rev cc429e84515a2f6bae05cd7cd81c3f622d0c8b57)
* maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java
> 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)