I created a ticket for the commons-configuration issue.. Can any tell me what Joerg's comment below implies?
Would the problem be fixed if we find an alternate source for the pom? ------- Forwarded message follows ------- Date sent: Sat, 16 Jul 2011 20:22:00 +0000 (UTC) From: "Joerg Schaible (JIRA)" <[email protected]> To: [email protected] Subject: [jira] [Commented] (CONFIGURATION-454) Malformed pom uploaded to repositories [ https://issues.apache.org/jira/browse/CONFIGURATION- 454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=13066530#comment-13066530 ] Joerg Schaible commented on CONFIGURATION-454: ---------------------------------------------- I think this is a left-over from a M1 POM where the POM was actually a Jelly script. Can't remember currently, but it might be that 1.6 was still released with M1 and the POM you're facing has been auto-converted" by Maven folks' repository tools. > Malformed pom uploaded to repositories > -------------------------------------- > > Key: CONFIGURATION-454 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-454 > Project: Commons Configuration > Issue Type: Bug > Components: Build > Affects Versions: 1.6 > Reporter: Kevin Meyer > Priority: Minor > Labels: maven > > The pom downloaded, for example, from: > http://uk.maven.org/maven2/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.pom > is damaged: e.g. the <url> is given as: > <url>http://commons.apache.org/${pom.artifactId.substring(8)}/</url> > <directory>${basedir}</directory> > etc. > This affects the generated licenses for other projects. > Compare with commons-collections, which is fine. > Problems seems to be in trunk/project.xml ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ------- End of forwarded message ------- --
