[weld-dev] Pom's in maven central referring to jboss org nexus :(

[Pete Muir]

On 21 Jul 2011, at 12:31, Max Rydahl Andersen wrote:

> Hi,
> 
> I was playing with mvn today and wanted to use:
> 
> <dependency>
> <groupId>org.jboss.spec</groupId>
> <artifactId>jboss-javaee-6.0</artifactId>   
> <version>1.0.0.Final</version>
> <type>pom</type>
> <scope>provided</scope>
> </dependency>
> 
> as described on http://community.jboss.org/wiki/WhatsTheCauseOfThisExceptionJavalangClassFormatErrorAbsentCode
> 
> And I wanted to see what happens when I *only* have maven central setup.
> 
> To my surprise I saw this in mvn log:
> 
> Downloaded: http://repo1.maven.org/maven2/javax/enterprise/cdi-api/1.0-SP4/cdi-api-1.0-SP4.pom (7 KB at 10.0 KB/sec)
> Downloading: http://repo1.maven.org/maven2/org/jboss/weld/weld-parent/17/weld-parent-17.pom
> Downloading: https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/weld-parent/17/weld-parent-17.pom
> Downloaded: https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/weld-parent/17/weld-parent-17.pom (31 KB at 4.1 KB/sec)
> 
> 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).

I guess this is now transitional, we can start to remove these declarations in updates to POMs as stuff get's moved to central. Max, could you make a WELD issue for this?