I think you should just move the <configuration/> element to be a
child inside <plugin/>, and then remove the <executions/> completely.
Wayne
On 7/24/06, Zeltner Martin <[EMAIL PROTECTED]> wrote:
Hello!
I have the following plugin config in my pom with packaging "jar":
-----------------------------------
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.1-SNAPSHOT</version>
<executions>
<execution>
<id>default</id>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<archive>
<manifestSections>
<manifestSection>
<name>el4j-config</name>
<manifestEntries>
<Module>${el4j-config.module}</Module>
<Files>${el4j-config.files}</Files>
<Dependencies>${el4j-config.dependencies}</Dependencies>
</manifestEntries>
</manifestSection>
</manifestSections>
</archive>
</configuration>
</execution>
</executions>
</plugin>
-----------------------------------
If I have a look at the console output when executing "mvn package" I
can see that goal "jar:jar" is executed twice. The first invokation
comes from the default jar lifecycle of my pom and the second from my
config above. Can someone tell me how to configure the plugin above that
the default jar lifecycle directly executes my execution-definition
(id=default)?
Thanks for your help in advance!
Cheers,
Martin
---------------------------------------------------------------------
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]
