www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <steve.lough...@gmail.com>
Subject bad group ID in commons-io?
Date Thu, 19 Nov 2009 11:52:44 GMT
Ivy is refusing to play with commons-io

[ivy:resolve] 		:: org.apache.commons#commons-io;1.3.2:
java.text.ParseException: inconsistent module descriptor file found in
'http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom':
bad organisation: expected='org.apache.commons' found='commons-io';
[ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve] :::: ERRORS
[ivy:resolve] 		maven2: bad organisation found in
http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom:
expected='org.apache.commons' found='commons-io'
[ivy:resolve]

Looking at the Pom, it may have a point

http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom:
<project>
<parent>
<artifactId>commons-parent</artifactId>
<groupId>org.apache.commons</groupId>
<version>3</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<name>Commons IO</name>
<version>1.3.2</version>

The parent group ID is set up right, but the artifact's own group is wrong.
* should Ivy be ignoring the artifact ID and go for the parent's?
* should the repository be rejecting artifacts whose group ID != their
location in the tree?

-steve

Mime
View raw message