Why don't you break your project up into 2 modules? One for your arr and one that is for your war. Then make your war depend on the arr.
I'm not familiar with arr, so this is only a guess... HTH Jim On 9/28/07, aldana <[EMAIL PROTECTED]> wrote: > > > hi, > > my app is from type war so implicitly the war-plugin gets executed as > first > plugin in package phase. > problem is that before building the war i need to package my axis2 > webservice-app as aar (which exists as own task). aar-plugin must > therefore > execute before war plugin. thus i cannot work with inherited behaviour of > war-packaging :( > > is there a workaround how to execute aar plugin before war plugin. my > first > ideas were to bind aar-plugin to phase before package which is not nice, > because aar task belongs to package phase. > second idea was to mark my webapp as jar-packaging, this makes > configuration > more lengthy but should somehow solve my problem. > > i already searched the mailinglist and this seems to be an issue, > especially > with war-packing. i think ordering of inherited plugins should be possible > to control. > -- > View this message in context: > http://www.nabble.com/how-to-disable-implicit-plugin-execution-order-of-inherited-poms--tf4534393s177.html#a12940156 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
