Maven
  1. Maven
  2. MNG-4453

[regression] Plugin versions defined in a lifecycle mapping are not respected

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0-alpha-4
    • Fix Version/s: 3.0-beta-1
    • Component/s: Plugins and Lifecycle
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      As reported by Sebastian Annies in Using a specific plugin version in custom lifecycle, the plugin version given by a lifecycle mapping like

      <verify>org.apache.maven.plugins:maven-source-plugin:2.1:jar-no-fork</verify>
      

      is not respected by Maven 3.0, it's preferring the version from the plugin management of the super POM instead.

        Activity

        Benjamin Bentmann made changes -
        Field Original Value New Value
        Assignee Benjamin Bentmann [ bentmann ]
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Fix Version/s 3.0-beta-1 [ 16089 ]

          People

          • Assignee:
            Benjamin Bentmann
            Reporter:
            Benjamin Bentmann
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: