Igor Fedorenko opened MNG-5768 and commented
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:
- MNG-3409 Add ability to execute an specific plugin execution via its id
("duplicates")
- MNG-5833 Invoking non-existant execution from command line executes default
Remote Links:
Igor Fedorenko opened MNG-5768 and commented
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-idparameter, e.g., org.apache.maven.plugins:maven-remote-resources-plugin:1.0:process@executionId.Issue Links:
("duplicates")
Remote Links: