when does the plugin goal get executed during the lifecycle

Posted on July 6, 2010 Leave a comment (3) Go to comments

[INFO] [clean:clean] [INFO] [ear:generate-application-xml] [INFO] [resources:resources] [INFO] [antrun:run {execution: fix.eclipse:eclipse-eclipseEAR.applicationXML}] [INFO] [ear:ear] [INFO] [source:jar {execution: default}] [INFO] [ear:ear {execution: default}] [INFO] [install:install] [INFO] [antrun:run {execution: default}] [INFO] Executing tasks [echo] Invoking explode ant target…

So by default the plugin goal executes *after* the phase (and final goal) it’s bound to…

Maven, , , , ,
Leave a comment

3 Comments.

  1. Stephen Connolly July 7, 2010 at 6:08 am

    The rule for Maven is that the order of plugin execution within a phase is undefined.

    -Stephen

  2. Anders Hammar July 7, 2010 at 6:18 am

    AFAIK it’s the order they are defined in in the pom. This would depend on the version of Maven though, as it has not always been like that.

    /Anders

  3. Stephen Connolly July 7, 2010 at 7:40 am

    AFAIK, the order only applies for plugins in the main build section, not plugins introduced via a profile, and the ordering is just a side effect. The recommendation is not to rely on the order within a phase, if something should run prior to something else, bind it to an earlier phase

    -Stephen

Leave a Reply