[jira] [Created] (CONFIGURATION-454) Malformed pom uploaded to repositories

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (CONFIGURATION-454) Malformed pom uploaded to repositories

ASF GitHub Bot (Jira)
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


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

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CONFIGURATION-454) Malformed pom uploaded to repositories

ASF GitHub Bot (Jira)

    [ 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 stilkl 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CONFIGURATION-454) Malformed pom uploaded to repositories

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

    [ 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CONFIGURATION-454) Malformed pom uploaded to repositories

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/CONFIGURATION-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100486#comment-13100486 ]

Kevin Meyer commented on CONFIGURATION-454:
-------------------------------------------

Sure - I'll try 1.7. Thanks for the heads-up.

> 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

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CONFIGURATION-454) Malformed pom uploaded to repositories

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/CONFIGURATION-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100497#comment-13100497 ]

Sebb commented on CONFIGURATION-454:
------------------------------------

Maven Central won't allow updates to jars etc. because that would mean builds were not repeatable.

They do allow hashes and sigs to be replaced, and they may allow the url to be fixed as it does not affect builds.

Worth reporting in case.

> 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