Created: (MEV-643) POMs on central repo with references to external repositories and/or plugin repositories

POMs on central repo with references to external repositories and/or plugin repositories
----------------------------------------------------------------------------------------

                 Key: MEV-643
                 URL: http://jira.codehaus.org/browse/MEV-643
             Project: Maven Evangelism
          Issue Type: Bug
          Components: Invalid POM
            Reporter: Stevo Slavic


There are numerous artifacts on central repo with POMs that reference external repositories and/or plugin repositories. Thereby these artifacts break rules from [upload to central guide|http://maven.apache.org/guides/mini/guide-central-repository-upload.html], rendering central repo to be non-self-contained.

Multitude of these artifacts have been uploaded to central after rules have been imposed (e.g. in year 2009), so there seems to be something wrong in rule validation process. Not sure if ability to sync repositories to central makes things worse.

From user perspective, most annoying issue for me at the moment is in case where project has direct or transitive dependencies to these artifacts, org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.2:dependencies report mojo when generating report will together with project defined repositories pickup these repositories from dependencies POMs, and use them all to check for existence of all artifacts, hanging build.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/MEV-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197316#action_197316 ]

Stevo Slavic commented on MEV-643:
----------------------------------

Here are some examples:

- org.apache:apache:6
- org.apache.cxf:cxf-rt-ws-security:2.2.4
- org.apache.geronimo.genesis.config:project-config:1.5
- org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4
- org.apache.maven.plugins:maven-resources-plugin:2.4.1
- org.apache.tiles:tiles-core:2.2.1
- org.codehaus.castor:castor:1.3.0.1
- org.codehaus.mojo:mojo-parent:22
- org.eclipse.jetty:jetty-parent:11
- org.slf4j:slf4j-parent:1.5.9.RC1
- org.springframework.webflow:spring-binding:2.0.8.RELEASE
- org.springframework.webflow:spring-webflow:2.0.8.RELEASE
- org.springframework.ws:spring-ws-parent:1.5.8
- org.springframework.ws:spring-ws-security:1.5.8

> POMs on central repo with references to external repositories and/or plugin repositories
> ----------------------------------------------------------------------------------------
>
>                 Key: MEV-643
>                 URL: http://jira.codehaus.org/browse/MEV-643
>             Project: Maven Evangelism
>          Issue Type: Bug
>          Components: Invalid POM
>            Reporter: Stevo Slavic
>
> There are numerous artifacts on central repo with POMs that reference external repositories and/or plugin repositories. Thereby these artifacts break rules from [upload to central guide|http://maven.apache.org/guides/mini/guide-central-repository-upload.html], rendering central repo to be non-self-contained.
> Multitude of these artifacts have been uploaded to central after rules have been imposed (e.g. in year 2009), so there seems to be something wrong in rule validation process. Not sure if ability to sync repositories to central makes things worse.
> From user perspective, most annoying issue for me at the moment is in case where project has direct or transitive dependencies to these artifacts, org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.2:dependencies report mojo when generating report will together with project defined repositories pickup these repositories from dependencies POMs, and use them all to check for existence of all artifacts, hanging build.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira