[weld-issues] [JBoss JIRA] Created: (WELD-754) Fix weld parent pom repository list

Fix weld parent pom repository list ----------------------------------- Key: WELD-754 URL: https://jira.jboss.org/browse/WELD-754 Project: Weld Issue Type: Bug Reporter: Sivakumar Thyagarajan The current weld parent pom (org.jboss.weld:weld-parent:pom:17) has a reference to the public repository http://repository.jboss.org/nexus/content/groups/public with the id "jboss-snapshots-repository". As per the documentation in http://community.jboss.org/wiki/MavenRepository, the public repository group has both snapshots and releases. - If a snapshots-only repository was only intended, could we use the /snapshots hosted repository available at https://repository.jboss.org/nexus/content/repositories/snapshots/. - On the other hand if the /public repository group was intended (ie both releases and snapshot), since the public repo group contains both releases and snapshots, could we fix line 41 and line 55 to enable releases? https://github.com/weld/parent/blob/17/pom.xml#L55 We had an issue recently because of the disabling of releases in line 55. Maven 2.0.10 is the minimum maven version for weld. When GlassFish added the JBoss public repository group to its nexus repo, if I used maven 2.0.10, when a maven artifact from the JBoss repo was obtained, all references from that maven artifact used the repository definition in weld-parent:pom. Since releases were disabled in this repo definition, the released artifact residing in JBoss repo could not be found. Maven 2.2.1 fixes this issue(and also consults the repo definition in GlassFish) and we use 2.2.1 now. However, it would be useful to fix this discrepancy in weld-parent POM. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira