I created a user proposal to hopefully clarify the issue and my proposed 
solution:
http://docs.codehaus.org/display/MAVENUSER/Default+Plugin+Execution+IDs

Paul Gier wrote:
Ok thanks, I attached a patch which is just a one line change to set the execution id to "default" if nothing is specified.

It fixes the issue for me, but I guess the concern is that it could change the behaviour for anyone currently using an id of "default" or not using an execution id. So I'm not sure if this is something that could go into 2.0.x or has to wait until 2.1.

Brian E. Fox wrote:
Yes, this is needed. I have a jira somewhere for it...
http://jira.codehaus.org/browse/MNG-3401


-----Original Message-----
From: Paul Gier [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2008 3:46 PM
To: Maven Developers List
Subject: Default plugin execution id

Hi everyone,

I'd like to be able to configure the default execution of a plugin
within an execution instead of doing it through the main plugin configuration. So
the result would look something like this:

<plugin>
   <groupId>org.apache.maven.plugins</groupId>
   <artifactId>maven-jar-plugin</artifactId>
   <executions>
     <execution>
       <id>default</id>
       <configuration>
         <includes>
           <include>stuff/**</include>
         </includes>
       </configuration>
     </execution>
     <execution>
       <id>custom</id>
       <configuration>
         <includes>
           <include>other-stuff/**</include>
         </includes>
       </configuration>
     </execution>
   </executions>
</plugin>

Currently, it seems the only way to configure the default jar plugin
execution is to use the main plugin configuration section. This doesn't work as well because it ends up applying the config to all executions, which is not
always what is needed.

Benjamin pointed me to the MojoExceution constructor which sets the id
to null, and PluginExecution from the model which sets the id to "default". This

difference seems to be why the default executions can't be overridden in
an execution config.

Any thoughts?  I'll create a jira issue with a patch for this, but I'll
wait for   feedback before changing anything.

Thanks!


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to