Bug 1013690

Summary:	Cannot run s-ramp-demos-switchyard quickstart (No connector available to access repository)
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Stefan Bunciak <sbunciak>
Component:	Examples, DT Governance	Assignee:	Kurt T Stam <kurt.stam>
Status:	CLOSED DUPLICATE	QA Contact:	Jiri Sedlacek <jsedlace>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, ldimaggi, oskutka, soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-15 00:44:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stefan Bunciak 2013-09-30 15:32:13 UTC

Description of problem:

* Maven build of s-ramp-demos-switchyard quickstart fails

Version-Release number of selected component (if applicable):
* 6.0.0.ER3

How reproducible:
* 100%

Steps to Reproduce:
1. Install FSW 6.0.0.ER3
2. cd to jboss-eap-6.1/quickstarts/sramp
3. execute maven -Pdemo clean deploy (according to the shipped README file)

Actual results:

* http://pastebin.test.redhat.com/167093

Expected results:


Additional info:

Comment 1 Stefan Bunciak 2013-09-30 15:50:19 UTC

2nd step to reproduce should be: cd to jboss-eap-6.1/quickstarts/sramp/s-ramp-demos-switchyard

Comment 2 Len DiMaggio 2013-09-30 16:40:44 UTC

Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5-redhat-1:deploy (default-deploy) on project s-ramp-demos-switchyard: Failed to deploy artifacts/metadata: No connector available to access repository local-sramp-repo (sramp://localhost:8080/s-ramp-server/?artifactType=SwitchYardApplication) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1]

Comment 3 Kurt T Stam 2013-10-15 00:44:04 UTC


*** This bug has been marked as a duplicate of bug 1016580 ***