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 2020/03/28 14:59:03 UTC

[jira] [Commented] (MNG-5768) specify execution-id for direct plugin goal invocation from command line

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

Hudson commented on MNG-5768:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> 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
>            Priority: Major
>             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
(v8.3.4#803005)