Repository metadata does not correctly indicate latest release

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 2.4.2
    • Affects Version/s: 2.4
    • Component/s: Maven plugin
    • None
    • Environment:

      maven 2.0.9

      The metadata in central [1] correctly indicates the <latest> version, but that 2.3.1 is the newest release. I assume the <release> value should be bumped.

      It's not a huge problem, but the fact that newer versions are numbered as a release but not so indicated seems to confuse some plugins: I have a project that is definitely building with Clover 2.4.1, but the Project Plugins report incorrectly indicates 2.3.1 was used.

      Note that this only occurs when the <version> is not specified in the POM for maven-clover2-plugin. Running "mvn clean verify site" on the attached project demonstrates the issue – note I did not include the clover.license.

      [1] http://repo1.maven.org/maven2/com/atlassian/maven/plugins/maven-clover2-plugin/maven-metadata.xml

        1. build-output-and-log.zip
          151 kB
        2. Proj.ZIP
          2 kB

            Assignee:
            James Dumay
            Reporter:
            Stephen Pack
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: