The project doesn't depend on a plugin from within the <dependencies>
section of the pom. I had to add this
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.0-beta-3-SNAPSHOT</version>
</plugin>
in the <build><plugins> to make m2 use the right version of the
maven-war-plugin. Without that, it will use the released version which
doesn't have the overlaying feature which I need.
Rich
Mike Perham wrote:
Why is your project depending on a plugin??? The project should be
configuring and using the plugin but not depending on it (i.e. it should
not be listed in <build><dependencies>).
-----Original Message-----
From: Richard Wallace [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 22, 2006 2:54 PM
To: Maven Users List
Subject: [m2] Next maven-war-plugin release?
Hello all,
I'm just wondering when we can expect the next release of the
maven-war-plugin. Right now I have a webapp project that depends on
another webapp project and uses the functionality of the snapshot
maven-war-plugin to be able to inherit stuff (JSPs, images, etc.) from
the 1st webapp. I want to do a release of my project with the
maven-release-plugin but it won't let me since there is a dependency on
a snapshot.
Any ideas when we can expect a release? Is there a way I can override
this behavior in the meantime?
Thanks,
Rich
---------------------------------------------------------------------
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]
