Bug 1015584

Summary:	S-RAMP Distribution deployment
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Nick Cross <ncross>
Component:	DT Governance	Assignee:	Eric Wittmann <eric.wittmann>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Stefan Bunciak <sbunciak>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	atangrin, eric.wittmann, gbrown, ldimaggi, soa-p-jira
Target Milestone:	ER7
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Nick Cross 2013-10-04 14:25:44 UTC

1. s-ramp-distro-assembly contains multiple assemblies to produce different zips. Can this be split into different modules e.g.
 s-ramp-distro-assembly
 s-ramp-distro-assembly-cli
 s-ramp-distro-assembly-demos
so that each zip can be deployed?

2. Can the deployment be enabled (even if via a profile) as that would mean we wouldn't have to patch the code.

Comment 2 Eric Wittmann 2013-10-04 15:13:53 UTC

I'm in favor of enabling deployment in all cases - no reason not to have the .zip in nexus.  I think we were trying to prevent large deployments from showing up there, but we should reconsider.

Comment 5 Eric Wittmann 2013-11-08 17:49:59 UTC

This has been done.  Additionally I moved the s-ramp-demos project up to the root of s-ramp, so it's now a direct child of s-ramp.

Comment 6 Stefan Bunciak 2014-01-16 11:19:54 UTC

Verified in FSW 6.0.0.ER8