[
https://issues.apache.org/jira/browse/CONFIGURATION-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100467#comment-13100467
]
Oliver Heger commented on CONFIGURATION-454:
--------------------------------------------
As far as I know, it is impossible to change artifacts in the central maven
repository after they have been uploaded. So I doubt that the problem can be
fixed for the 1.6 pom.
However, version 1.7 has just been released. The pom in maven central looks
good. Can you update your dependency to this version? (It should be a drop-in
replacement for 1.6.)
> 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
