[
http://jira.codehaus.org/browse/MEV-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juven Xu closed MEV-643.
------------------------
Resolution: Won't Fix
Assignee: Juven Xu
since those artifacts are already in central, update those POM might break
people's builds
yes it's not good to have repo/pluginRepo in POM, and we are trying to improve
the process to stop people doing things like this.
eg:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.2.PublishSnapshots
So closing this issue as won't fix.
> 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
> Assignee: Juven Xu
>
> 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
