Bug 849694

Summary:	Remove Rubygems from WFK Maven repository
Product:	[Retired] JBoss Enterprise WFK Platform 2	Reporter:	Ben Browning <bbrownin>
Component:	TorqueBox	Assignee:	Marek Novotny <mnovotny>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Oliver Kišš <okiss>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	2.0.0.GA	CC:	djorm, kpiwko, mnovotny, oskutka
Target Milestone:	ER1
Target Release:	2.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-30 15:34:26 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 Ben Browning 2012-08-20 15:38:27 UTC

Right now Rubygems needed to build TorqueBox (rails, activerecord, json, etc) are making their way into the Maven repository shipped to customers as part of WFK. These need to be split out into a separate repository so that QE can run integration tests against TorqueBox without these gems making their want into the hands of the customer.

Comment 1 Marek Novotny 2012-09-25 10:06:14 UTC

I split the WFK repository into 2 zipped files. New one is jboss-wfk-2.1.0.ER1-maven-repository-compilation.zip

That zip file now contains only rubygems.

Comment 2 Karel Piwko 2012-11-30 15:34:26 UTC

Distributed as a part of WFK 2.1.0.GA release.