[
https://jira.codehaus.org/browse/MNG-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326727#comment-326727
]
Thomas Champagne edited comment on MNG-5420 at 6/14/13 2:16 AM:
----------------------------------------------------------------
I think this issue is duplicated with MNG-3409. Or, do you want to run other
execution id in the default-cli mechanism.
It would be nice to run an execution id in other goal.
An example with sql-maven-plugin :
{code:xml}
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>sql-maven-plugin</artifactId>
<executions>
<execution>
<id>drop-schemas-before-unit-test</id>
<phase>process-test-resources</phase>
<goals>
<goal>execute</goal>
</goals>
</execution>
<execution>
<id>create-database</id>
<phase>process-test-resources</phase>
<goals>
<goal>execute</goal>
</goals>
</execution>
<execution>
<id>default-execute</id>
<goals>
<goal>drop-schemas-before-unit-test</goal>
<goal>create-database</goal>
</goals>
</execution>
</executions>
</plugin>
{code}
was (Author: lafeuil):
I think this issue is duplicated with MNG-3409
> Need to be able to specify running a specific execution by id
> -------------------------------------------------------------
>
> Key: MNG-5420
> URL: https://jira.codehaus.org/browse/MNG-5420
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 3.0.4
> Reporter: Sebastien Tardif
>
> The limitation of not been able to specify executing an execution id of a
> plug-in is often mentioned.
> It's very obvious to be a missing feature when you are using a plug-ins that
> is generic like maven-antrun-plugin or maven*groovy.
> In other words, I may have a tiny ant script deleting some folders, then
> still also need the maven-antrun-plugin for other things like preparing a DB.
> It's insane to be stuck with only default-cli mechanism when all my
> "execution"s already have an identifier.
> Instead of been stuck with antrun:run, I should be able to do
> antrun:myExecutionId
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
