That's usually a sign that you have wandered off The Maven Way™ There are ways back onto the blessed path... they typically involve writing a plugin
On 4 June 2014 16:47, jhgnwea <[email protected]> wrote: > Paul Benedict wrote > > I agree with Dan. Last I check, IIRC, the order of operations of plugins > > is > > defined by their sequential order in the POM. However, I also find this a > > bit problematic with inheritance -- I don't know off the top of my head > > what happens then. > > Ordering applies only for executions of a single plugin. If you need to > interleave executions of two or more plugins you're out of luck. Say you > have two plugins, exec-maven and maven-sql, and want to run > > exec-maven A1 > maven-sql B1 > exec-maven A2 > maven-sql B2 > > A1 and A2 will run in that order, and (B1, B2) will be ordered, but you > can't control which set (A or B) runs first without horribly abusing the > phase bindings. And, if you have a more complex sequence with 3 plugins > and multiple executions of each, there aren't enough available phases to > successfully order everything. > > It should be possible to bind multiple plugin executions, of DIFFERENT > plugins, to a single phase and deterministically specify the execution > order. > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Controlling-order-of-plugin-execution-tp5794777p5794892.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
