commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (IO-347) org.apache.commons:commons-io:1.3.2 POM is broken
Date Fri, 05 Oct 2012 09:51:02 GMT


Sebb commented on IO-347:

The problem is that 1.3.2 was accidentally copied into the wrong source directory at Apache
from whence it was deployed.
[It seems Maven Central had/has no check to ensure that the coordinates and directory agree
with each other]

I've looked, and the Apache Nexus repo currently has both entries.

I think there are two stages to fixing this:
1) remove incorrect entry from Apache Nexus (INFRA-5359 created for this)
2) persuade Maven Central to drop the incorrect entry.

> org.apache.commons:commons-io:1.3.2 POM is broken
> -------------------------------------------------
>                 Key: IO-347
>                 URL:
>             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
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
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:

View raw message