Thanks for the clarification, Benjamin. Does this mean that it's not possible to force a plugin to execute in the compile phase and before the default-compile execution unless I write a custom lifecycle and use a different packaging type?
Cheers, Graham. On 10/05/2011, at 7:23 AM, Benjamin Bentmann <[email protected]> wrote: > Wendy Smoak wrote: > >> Isn't there a super pom baked inside Maven that everything implicitly >> inherits from? > > Yes. > >> I wonder if the order is coming from that... > > No, the rules for the plugin ordering game within a given phase are > 1) plugins from lifecycle mappings go first > 2) plugins from the POMs go in order of appearance in effective POM > > > Benjamin > > --------------------------------------------------------------------- > 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]
