I don't think anyone is generally going to type:
default-execution-id
It says what it is and if someone happens to look at the effective POM
they will understand. It's also unlikely someone would actually use
that in their own POMs.
On 8-Nov-08, at 2:23 AM, Benjamin Bentmann wrote:
Brett Porter wrote:
How about #groupId:artifactId:sequenceNumber.
What would be the sequenceNumber part? This kind of execution config
is surely an edge case but I would prefer the execution id to not be
too complex/cryptic (someday I might want to type it into the POM...).
It would be unique to the POM.
AFAIK, execution ids were meant to assist in merging inherited
configuration. As this happens on a per plugin basis, we don't have
need for ids which are unique to the entire POM, do we?
Besides, I start wondering how this relates to MNG-3203. Assuming
for a moment
a) there is one execution per plugin goal and
b) the implicit execution ids where equal to the executed plugin goal
it seems something like
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<executions>
<execution>
<id>compile</id>
<configuration>
<!-- parameters for main compilation here -->
</configuration>
</execution>
<execution>
<id>testCompile</id>
<configuration>
<!-- parameters for test compilation here -->
</configuration>
</execution>
</executions>
</plugin>
would naturally extend Paul's original use case.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
the course of true love never did run smooth ...
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
