I have no idea if its a bug or not, but a way to fix things would be to simply add another level of parent in the project under which all your war projects are located.
Thus: top-parent + war-parent ++ war-project1 ++ war-project2 ++ war-project3 Then tell your war-projects to use war-parent as its parent, and set the configuration inside it. Wayne On 3/19/08, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Wed, Mar 19, 2008 at 6:51 AM, Kees van Dieren > <[EMAIL PROTECTED]> wrote: > > > In our root pom.xml we have the maven war plugin defined: > ... > > On mvn package, it will run mvn war:inplace, but not only for war > > artifacts, > > but also for jar artifacts. > > > > How can we make this execution only applicable for projects with packaging > > war? > > Is it a bug in the war plugin perhaps? Should it somehow "know" not > to run in the jar modules? > > If you don't get more info here, I'd construct a simple example to > demonstrate when it does the wrong thing, and attach it to an issue in > JIRA. http://jira.codehaus.org/browse/MWAR > > -- > Wendy > > --------------------------------------------------------------------- > 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]
