commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IO-347) commons-io:commons-io:1.3.2 POM incorrectly deployed under org.apache.commons
Date Fri, 05 Oct 2012 09:53:03 GMT

     [ https://issues.apache.org/jira/browse/IO-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb updated IO-347:
--------------------

    Summary: commons-io:commons-io:1.3.2 POM incorrectly deployed under org.apache.commons
 (was: org.apache.commons:commons-io:1.3.2 POM is broken)
    
> commons-io:commons-io:1.3.2 POM incorrectly deployed under org.apache.commons
> -----------------------------------------------------------------------------
>
>                 Key: IO-347
>                 URL: https://issues.apache.org/jira/browse/IO-347
>             Project: Commons IO
>          Issue Type: Bug
>    Affects Versions: 1.3.2
>            Reporter: Mirko Friedenhagen
>
> As already discussed a bit on IO-125 and related to https://issues.sonatype.org/browse/MVNCENTRAL-244:
> http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom
has a incorrect {{groupId}} {{commons-io}}, Artifactory e.g. complains about this.
> AFAIS the artifacts at org/apache/commons have the same checksums as those at commons-io.
As a workaround I deployed a relocation POM https://raw.github.com/gist/3832570/ac0c2503cea5e8642035eae0904fab4ad2fb74f3/commons-io-1.3.2.pom
in a repository which is searched before central in my Artifactory instance.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message