|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
POMs on central repo with references to other repositoriesHello Maven users,
By this guide<http://maven.apache.org/guides/mini/guide-central-repository-upload.html>it seems to be forbidden to upload artifacts to central with POMs that reference other repositories, so that central repo is self-contained. Even with this rule there seem to be many artifacts on central which reference non-central repositories. Dependencies report mojo from maven-project-info-reports plugin seems to pick up these repositories declared in dependencies too, displaying build-hanging warnings on them like "[WARNING] The repository url 'http://maven.springframework.org/external' is invalid - Repository 'spring-external' will be blacklisted." (btw http://maven.springframework.org/external repository is defined in org.springframework.ws:spring-ws-parent) Will central be cleaned up from these artifacts? Is there an issue where one could report such invalid POMs? Is the policy regarding repository references different when external repositories are being synced to central? Regards, Stevo. |
|
|
Re: POMs on central repo with references to other repositoriesMy understanding is:
1) No, central will not be cleaned. No changes are done to central as it might break builds. 2) http://jira.codehaus.org/browse/MEV 3) I don't think so. The pom(s) you've found are old ones before the rules were enforced (or even existed possibly) /Anders On Wed, Nov 4, 2009 at 11:58, Stevo Slavić <sslavic@...> wrote: > Hello Maven users, > > By this guide< > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > >it > seems to be forbidden to upload artifacts to central with POMs that > reference other repositories, so that central repo is self-contained. Even > with this rule there seem to be many artifacts on central which reference > non-central repositories. Dependencies report mojo from > maven-project-info-reports plugin seems to pick up these repositories > declared in dependencies too, displaying build-hanging warnings on them > like > > > "[WARNING] The repository url 'http://maven.springframework.org/external' > is > invalid - Repository 'spring-external' will be blacklisted." > > (btw http://maven.springframework.org/external repository is defined in > org.springframework.ws:spring-ws-parent) > > Will central be cleaned up from these artifacts? > Is there an issue where one could report such invalid POMs? > Is the policy regarding repository references different when external > repositories are being synced to central? > > Regards, > Stevo. > |
|
|
Re: POMs on central repo with references to other repositoriesOK, thanks!
I believe these rules existed before year 2009. Here<http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/>is one such pom<http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/spring-ws-parent-1.5.8.pom>uploaded in August 2009, and another one<http://repo2.maven.org/maven2/org/codehaus/castor/castor/1.3.0.1/castor-1.3.0.1.pom>uploaded in September 2009., org.apache:apache:6:pom from April 2009 has external snapshot repo, jetty-parent:11 pom<http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-parent/11/jetty-parent-11.pom>from July 2009 has both external repositories and pluginRepositories defined, ... Regards, Stevo. On Wed, Nov 4, 2009 at 12:54 PM, Anders Hammar <anders@...> wrote: > My understanding is: > > 1) No, central will not be cleaned. No changes are done to central as it > might break builds. > 2) http://jira.codehaus.org/browse/MEV > 3) I don't think so. The pom(s) you've found are old ones before the rules > were enforced (or even existed possibly) > > /Anders > > On Wed, Nov 4, 2009 at 11:58, Stevo Slavić <sslavic@...> wrote: > > > Hello Maven users, > > > > By this guide< > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > >it > > seems to be forbidden to upload artifacts to central with POMs that > > reference other repositories, so that central repo is self-contained. > Even > > with this rule there seem to be many artifacts on central which reference > > non-central repositories. Dependencies report mojo from > > maven-project-info-reports plugin seems to pick up these repositories > > declared in dependencies too, displaying build-hanging warnings on them > > like > > > > > > "[WARNING] The repository url 'http://maven.springframework.org/external > ' > > is > > invalid - Repository 'spring-external' will be blacklisted." > > > > (btw http://maven.springframework.org/external repository is defined in > > org.springframework.ws:spring-ws-parent) > > > > Will central be cleaned up from these artifacts? > > Is there an issue where one could report such invalid POMs? > > Is the policy regarding repository references different when external > > repositories are being synced to central? > > > > Regards, > > Stevo. > > > |
|
|
Re: POMs on central repo with references to other repositoriesOk, it could be that these rules are still enforced by manual checking
today. There was a thread about this some weeks ago. Reporting these issues would be good, I guess. It makes it possible to address any future releases of these artifacts. /Anders On Wed, Nov 4, 2009 at 13:29, Stevo Slavić <sslavic@...> wrote: > OK, thanks! > > I believe these rules existed before year 2009. > Here< > http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/ > >is > one such > pom< > http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/spring-ws-parent-1.5.8.pom > >uploaded > in August 2009, and another > one< > http://repo2.maven.org/maven2/org/codehaus/castor/castor/1.3.0.1/castor-1.3.0.1.pom > >uploaded > in September 2009., org.apache:apache:6:pom from April 2009 has > external snapshot repo, jetty-parent:11 > pom< > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-parent/11/jetty-parent-11.pom > >from > July 2009 has both external repositories and pluginRepositories > defined, ... > > Regards, > Stevo. > > On Wed, Nov 4, 2009 at 12:54 PM, Anders Hammar <anders@...> wrote: > > > My understanding is: > > > > 1) No, central will not be cleaned. No changes are done to central as it > > might break builds. > > 2) http://jira.codehaus.org/browse/MEV > > 3) I don't think so. The pom(s) you've found are old ones before the > rules > > were enforced (or even existed possibly) > > > > /Anders > > > > On Wed, Nov 4, 2009 at 11:58, Stevo Slavić <sslavic@...> wrote: > > > > > Hello Maven users, > > > > > > By this guide< > > > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > > >it > > > seems to be forbidden to upload artifacts to central with POMs that > > > reference other repositories, so that central repo is self-contained. > > Even > > > with this rule there seem to be many artifacts on central which > reference > > > non-central repositories. Dependencies report mojo from > > > maven-project-info-reports plugin seems to pick up these repositories > > > declared in dependencies too, displaying build-hanging warnings on them > > > like > > > > > > > > > "[WARNING] The repository url ' > http://maven.springframework.org/external > > ' > > > is > > > invalid - Repository 'spring-external' will be blacklisted." > > > > > > (btw http://maven.springframework.org/external repository is defined > in > > > org.springframework.ws:spring-ws-parent) > > > > > > Will central be cleaned up from these artifacts? > > > Is there an issue where one could report such invalid POMs? > > > Is the policy regarding repository references different when external > > > repositories are being synced to central? > > > > > > Regards, > > > Stevo. > > > > > > |
|
|
Re: POMs on central repo with references to other repositoriesIssue <http://jira.codehaus.org/browse/MEV-643> reported.
Regards, Stevo. On Wed, Nov 4, 2009 at 1:38 PM, Anders Hammar <anders@...> wrote: > Ok, it could be that these rules are still enforced by manual checking > today. There was a thread about this some weeks ago. > Reporting these issues would be good, I guess. It makes it possible to > address any future releases of these artifacts. > > /Anders > > On Wed, Nov 4, 2009 at 13:29, Stevo Slavić <sslavic@...> wrote: > > > OK, thanks! > > > > I believe these rules existed before year 2009. > > Here< > > > http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/ > > >is > > one such > > pom< > > > http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/spring-ws-parent-1.5.8.pom > > >uploaded > > in August 2009, and another > > one< > > > http://repo2.maven.org/maven2/org/codehaus/castor/castor/1.3.0.1/castor-1.3.0.1.pom > > >uploaded > > in September 2009., org.apache:apache:6:pom from April 2009 has > > external snapshot repo, jetty-parent:11 > > pom< > > > http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-parent/11/jetty-parent-11.pom > > >from > > July 2009 has both external repositories and pluginRepositories > > defined, ... > > > > Regards, > > Stevo. > > > > On Wed, Nov 4, 2009 at 12:54 PM, Anders Hammar <anders@...> > wrote: > > > > > My understanding is: > > > > > > 1) No, central will not be cleaned. No changes are done to central as > it > > > might break builds. > > > 2) http://jira.codehaus.org/browse/MEV > > > 3) I don't think so. The pom(s) you've found are old ones before the > > rules > > > were enforced (or even existed possibly) > > > > > > /Anders > > > > > > On Wed, Nov 4, 2009 at 11:58, Stevo Slavić <sslavic@...> wrote: > > > > > > > Hello Maven users, > > > > > > > > By this guide< > > > > > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > > > >it > > > > seems to be forbidden to upload artifacts to central with POMs that > > > > reference other repositories, so that central repo is self-contained. > > > Even > > > > with this rule there seem to be many artifacts on central which > > reference > > > > non-central repositories. Dependencies report mojo from > > > > maven-project-info-reports plugin seems to pick up these repositories > > > > declared in dependencies too, displaying build-hanging warnings on > them > > > > like > > > > > > > > > > > > "[WARNING] The repository url ' > > http://maven.springframework.org/external > > > ' > > > > is > > > > invalid - Repository 'spring-external' will be blacklisted." > > > > > > > > (btw http://maven.springframework.org/external repository is defined > > in > > > > org.springframework.ws:spring-ws-parent) > > > > > > > > Will central be cleaned up from these artifacts? > > > > Is there an issue where one could report such invalid POMs? > > > > Is the policy regarding repository references different when external > > > > repositories are being synced to central? > > > > > > > > Regards, > > > > Stevo. > > > > > > > > > > |
|
|
Re: POMs on central repo with references to other repositoriesUnfortunately the rules currently are only checked for things uploaded
by hand, which is a tiny portion. The rsync sources that get setup are now checked when they are enabled, but things come directly in from the projects and it's not enforced. We're working on ways to correct this and stop the garbage. On Wed, Nov 4, 2009 at 4:38 AM, Anders Hammar <anders@...> wrote: > Ok, it could be that these rules are still enforced by manual checking > today. There was a thread about this some weeks ago. > Reporting these issues would be good, I guess. It makes it possible to > address any future releases of these artifacts. > > /Anders > > On Wed, Nov 4, 2009 at 13:29, Stevo Slavić <sslavic@...> wrote: > >> OK, thanks! >> >> I believe these rules existed before year 2009. >> Here< >> http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/ >> >is >> one such >> pom< >> http://repo1.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.8/spring-ws-parent-1.5.8.pom >> >uploaded >> in August 2009, and another >> one< >> http://repo2.maven.org/maven2/org/codehaus/castor/castor/1.3.0.1/castor-1.3.0.1.pom >> >uploaded >> in September 2009., org.apache:apache:6:pom from April 2009 has >> external snapshot repo, jetty-parent:11 >> pom< >> http://repo1.maven.org/maven2/org/eclipse/jetty/jetty-parent/11/jetty-parent-11.pom >> >from >> July 2009 has both external repositories and pluginRepositories >> defined, ... >> >> Regards, >> Stevo. >> >> On Wed, Nov 4, 2009 at 12:54 PM, Anders Hammar <anders@...> wrote: >> >> > My understanding is: >> > >> > 1) No, central will not be cleaned. No changes are done to central as it >> > might break builds. >> > 2) http://jira.codehaus.org/browse/MEV >> > 3) I don't think so. The pom(s) you've found are old ones before the >> rules >> > were enforced (or even existed possibly) >> > >> > /Anders >> > >> > On Wed, Nov 4, 2009 at 11:58, Stevo Slavić <sslavic@...> wrote: >> > >> > > Hello Maven users, >> > > >> > > By this guide< >> > > >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html >> > > >it >> > > seems to be forbidden to upload artifacts to central with POMs that >> > > reference other repositories, so that central repo is self-contained. >> > Even >> > > with this rule there seem to be many artifacts on central which >> reference >> > > non-central repositories. Dependencies report mojo from >> > > maven-project-info-reports plugin seems to pick up these repositories >> > > declared in dependencies too, displaying build-hanging warnings on them >> > > like >> > > >> > > >> > > "[WARNING] The repository url ' >> http://maven.springframework.org/external >> > ' >> > > is >> > > invalid - Repository 'spring-external' will be blacklisted." >> > > >> > > (btw http://maven.springframework.org/external repository is defined >> in >> > > org.springframework.ws:spring-ws-parent) >> > > >> > > Will central be cleaned up from these artifacts? >> > > Is there an issue where one could report such invalid POMs? >> > > Is the policy regarding repository references different when external >> > > repositories are being synced to central? >> > > >> > > Regards, >> > > Stevo. >> > > >> > >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |