[ https://issues.apache.org/jira/browse/MNG-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964929#comment-15964929 ]
ASF GitHub Bot commented on MNG-5768: ------------------------------------- Github user pono closed the pull request at: https://github.com/apache/maven-site/pull/7 > 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.15#6346)