Description of problem: Logging this bugzilla now as it may be affected by the other beta repo issues: https://bugzilla.redhat.com/show_bug.cgi?id=1007423 https://bugzilla.redhat.com/show_bug.cgi?id=1007436 Should we be writing references to community repos into the pom.xml files of projects that we create with product bits? Version-Release number of selected component (if applicable): SOA6.ER2 How reproducible: 100% Steps to Reproduce: 1. Create a new SwitchYard project 2. 3. Actual results: See the attached pom.xml file: <repository> <id>jboss-public-repository</id> <name>JBoss Public Maven Repository</name> <url>http://repository.jboss.org/nexus/content/groups/public</url> </repository> Expected results: Additional info:
Created attachment 796955 [details] pom file
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1701 Using settings.xml is a pain and it bites more users than it helps. Also, artifacts related to product have a unique version suffix, so I'm not sure how having the JBoss Nexus repository definition in the pom could possibly resolve product artifacts via this definition. Now that I have that off my chest ... :-) We are going to sync the 1.1 release artifacts to central, so this repo definition won't be necessary in community or product after that.
Keith - we got quickfixes in JBoss Tools to edit/quickfix users settings.xml. That is what we do for maven.repository.redhat.com. But general problem is more than just jboss.org being in pom.xml's its also how does users know which is the right version to use and how do they/we ensure they use the product bits ?
I definitely agree about making sure the correct version is used, regardless of the repositories defined in the pom.xml (which will go away) or settings.xml. Rob and I had chatted at one point of having a product filter (or branch) over the tooling which would only show users the product versions when creating a new project. Right now, there's a fairly large list of community versions presented to the user in the new project wizard.
Max Rydahl Andersen <manderse> made a comment on jira SWITCHYARD-1701 where is FSW ER4 directory ?
*** This bug has been marked as a duplicate of bug 965097 ***
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1701 pushed
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1701 to Closed