Maven doesn't have a good solution for this. The choice is either change the poms in our repository or tell people not to put repos in the poms, but Nexus doesn't have a way to enforce this.
Max Rydahl Andersen <[email protected]> wrote: >>> And yes it seems weld-parent explicitly lists repository.jboss.org in its >>> parent pom forcing this repo to be used for resolving dependencies afaics. >>> >>> Even if I have nexus configured to control my dependencies it will visit >>> that ;( >>> >>> I thought mirroring to maven central would not allow this to happen ? >> >> That rule got dropped about a year ago (maybe 18 months) due to the >> impracticality of it). > >And here I thought it was an excellent rule since it forces cleaner artifacts >instead of this situation ;( > >> I guess this is now transitional, we can start to remove these declarations >> in updates to POMs as stuff get's moved to central. > >Well, reproducible builds are to me more important than lazy pom's ;) > >Much better to have a settings.xml committed if its ease of use you want for >those building. > >> Max, could you make a WELD issue for this? > >I've created https://issues.jboss.org/browse/WELD-948 > >Just to check I searched for other references and found the additional >problems: > >CDI API: javax/enterprise/cdi-api/1.0-SP4/cdi-api-1.0-SP4.pom >JBoss EE 6: >org/jboss/spec/jboss-javaee-6.0/1.0.0.Final/jboss-javaee-6.0-1.0.0.Final.pom >RestEasy: >org/jboss/resteasy/resteasy-jaxrs-all/2.1.0.GA/resteasy-jaxrs-all-2.1.0.GA.pom >(actually have about multiple external repos declared) > >Paul - is this really what we want for our mirroring to maven central ? I >thought these things had to be cleaned up? > >We should get documented how users need to be careful about these - especially >if this also leaks into AS7/EAP6 and dependent builds... > >/max >http://about.me/maxandersen > > > _______________________________________________ weld-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-dev
