Uploaded image for project: 'Community Support - Maven Central'
  1. Community Support - Maven Central
  2. MVNCENTRAL-244

org.apache.commons:commons-io:1.3.2 POM is broken (or path is wrong :-))

    XMLWordPrintable

    Details

    • Type: Problem
    • Status: Done
    • Priority: Major
    • Component/s: None
    • Labels:
      None

      Description

      Taking a look at the POM at http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom, the groupId and artifactId are different from the deploy path and it seems the identical artifacts are available at http://repo1.maven.org/maven2/commons-io/commons-io/1.3.2/

      Having the same classes available under two different GAV coordinates may lead to a lot of problems should one decide to update the component to a new version. I see a lot of old builds could break when we delete from the old coordinates, but what about a (correct) relocation POM? Builds would continue to work and the mishap would appear on the screen.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            mfriedenhagen Mirko Friedenhagen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                tigCommentSecurity.panel-title