Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-5768

specify execution-id for direct plugin goal invocation from command line

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.1
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Issue Links

          Activity

          Show
          igorf Igor Fedorenko added a comment - https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=ee7dbab69dd87d219031b0715105527cdbf12639
          Hide
          githubbot ASF GitHub Bot added a comment -

          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 <francois.marot@gmail.com>
          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.


          Show
          githubbot ASF GitHub Bot added a comment - 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 <francois.marot@gmail.com> 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.
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user pono closed the pull request at:

          https://github.com/apache/maven-site/pull/7

          Show
          githubbot ASF GitHub Bot added a comment - Github user pono closed the pull request at: https://github.com/apache/maven-site/pull/7

            People

            • Assignee:
              igorfie igorfie
              Reporter:
              igorf Igor Fedorenko
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development