jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2 & 3
  • MNG-4341

[regression] Plugins are not executed in POM order

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major 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

Bug - A problem which impairs or prevents the functions of the product. MNG-2258 Wrong execution order of plugins in same phase

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-4344 [regression] Managed executions of plugins introduced by default lifecycle bindings execute before explicitly defined plugins

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MNG-4345 [regression] Plugin executions contributed by default lifecycle mapping execute after other plugin executions bound to the same phase

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Benjamin Bentmann added a comment - 07/Sep/09 2:16 PM

Fixed in r812259.

Show
Benjamin Bentmann added a comment - 07/Sep/09 2:16 PM Fixed in r812259.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Benjamin Bentmann
Vote (0)
Watch (0)

Dates

  • Created:
    07/Sep/09 9:09 AM
    Updated:
    21/Jun/10 1:50 PM
    Resolved:
    07/Sep/09 2:16 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.