[weld-issues] [JBoss JIRA] Created: (WELD-948) Weld parent points to jboss nexus in repository settings

Weld parent points to jboss nexus in repository settings -------------------------------------------------------- Key: WELD-948 URL: https://issues.jboss.org/browse/WELD-948 Project: Weld Issue Type: Bug Reporter: Max Rydahl Andersen Priority: Critical 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/WhatsTheCauseOfThisExceptionJavalangClass... 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.... (7 KB at 10.0 KB/sec) Downloading: http://repo1.maven.org/maven2/org/jboss/weld/weld-parent/17/weld-parent-1... Downloading: https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/w... Downloaded: https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/w... (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 ;( Our pom's should not force the choice of repository. Please re-release without these references. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira