[
https://issues.apache.org/jira/browse/MNG-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530998#comment-15530998
]
ASF GitHub Bot commented on MNG-5768:
-------------------------------------
GitHub user fmarot opened a pull request:
https://github.com/apache/maven-site/pull/7
Corrected assumption regarding execution's configuration
Corrected a wrong assumption saying that specific plugin's execution's
configuration could not be used from the command line.
This used to be true but not since Maven 3.3.1 and the implementation of
MNG-5768 ( https://issues.apache.org/jira/browse/MNG-5768 ).
From the command-line, the use of the specific syntax with "@" specifying a
specific execution (instead of "default-cli) will make the plugin's execution's
specific <configuration> section used.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fmarot/maven-site
fmarot-plugin-execution-asumption
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-site/pull/7.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #7
----
commit 69a4297f1ec9a1f53472d4879dd9d5ad8a9f2d1d
Author: Francois Marot <[email protected]>
Date: 2016-09-28T21:50:50Z
Corrected assumption regarding execution's configuration
Corrected a wrong assumption saying that specific plugin's execution's
configuration could not be used from the command line.
This used to be true but not since Maven 3.3.1 and the implementation of
MNG-5768 ( https://issues.apache.org/jira/browse/MNG-5768 ).
From the command-line, the use of the specific syntax with "@" specifying a
specific execution (instead of "default-cli) will make the plugin's execution's
specific <configuration> section used.
----
> specify execution-id for direct plugin goal invocation from command line
> ------------------------------------------------------------------------
>
> Key: MNG-5768
> URL: https://issues.apache.org/jira/browse/MNG-5768
> Project: Maven
> Issue Type: Improvement
> Reporter: Igor Fedorenko
> Assignee: igorfie
> Fix For: 3.3.1
>
>
> When invoking plugin goal from command line, it is possible to configure the
> goal using special 'default-cli' pom.xml execution id. This has two obvious
> limitations. First, it is not possible to have more than one configuration
> for command line use. Second, it is not possible to share configuration
> between direct plugin invocation and execution bound to lifecycle phase.
> To address this, I propose to extend direct plugin invocation syntax to allow
> optional @execution-id parameter, e.g.,
> org.apache.maven.plugins:maven-remote-resources-plugin:1.0:process@executionId.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
