Description of problem: Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1007423 In order for FSW6.beta customers to reliably build applications, they must have access to (and configure in settings.xml) these repositories: EAP 6.0 EAP 6.0.1 EAP 6.1 FSW 6.0.beta We need to provide off-line beta users with a zipp'ed repo that they can easily download and install - and a sample/template settings.xml to reference that downloaded zip. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.
Max Rydahl Andersen <manderse> made a comment on jira SWITCHYARD-1701 where is FSW ER4 directory ?
FSW ER4 has been released with a 4GB trim repo (http://dev138.mw.lab.eng.bos.redhat.com/candidate/soa-6.0.0-ER4).
Verified http://dev138.mw.lab.eng.bos.redhat.com/candidate/soa-6.0.0-ER4/ip-6.0.0.ER4-redhat-1-repo-trim.zip
Install the JBoss Integration Maven Repository Locally [22403] added.
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1701 pushed
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1701 to Closed