Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0-alpha-3
-
Fix Version/s: 3.0-alpha-3
-
Component/s: Plugins and Lifecycle, POM
-
Labels:None
-
Complexity:Intermediate
Description
The Selenium Maven Plugin declares
<plugin> <groupId>org.codehaus.groovy.maven</groupId> <artifactId>gmaven-plugin</artifactId> <executions> <execution> <goals> <goal>generateStubs</goal> <goal>compile</goal> <goal>generateTestStubs</goal> <goal>testCompile</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-plugin-plugin</artifactId> <executions> <execution> <goals> <goal>descriptor</goal> <goal>helpmojo</goal> </goals> </execution> </executions> </plugin>
i.e. with the gmaven-plugin preceeding the maven-plugin-plugin, yet trunk executes maven-plugin-plugin:helpmojo first, causing it to fail due to "No mojo definitions". The mojos get generated during gmaven-plugin:generateStubs.
Issue Links
- relates to
-
MNG-2258
Wrong execution order of plugins in same phase
-
-
MNG-4344
[regression] Managed executions of plugins introduced by default lifecycle bindings execute before explicitly defined plugins
-
-
MNG-4345
[regression] Plugin executions contributed by default lifecycle mapping execute after other plugin executions bound to the same phase
-
Fixed in r812259.