Bug 778680 (SOA-1150)

Summary:	SOA testing hard for project teams
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Julian Coleman <jcoleman>
Component:	Build Process	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP01
Target Milestone:	---
Target Release:	CONTINUING
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1150
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	N/A
Last Closed:	2010-07-28 20:28:30 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Julian Coleman 2009-01-27 11:40:39 UTC

Date of First Response: 2009-02-11 06:11:31
project_key: SOA

It is hard for project teams to test against the SOA platform, as the SOA platform build process is hard for
project members to use.

Solutions:
  1.  Give project members access to the SOA private repository
  2.  Change the way EAP is provided (e.g. by using ivy instead of SVN) to decrease the download size
  3.  Use anonsvn for project checkouts (* make this configurable)
  4.  Provide instructions for building the platform and for updating project versions

Comment 1 Julian Coleman 2009-01-30 10:57:43 UTC

Thomas Benninger has informed us that the SOA platform SVN server will move, and that
anonsvn will be available at some point on this new server.  This will solve point 1., above.

Comment 2 Thomas Diesler 2009-02-11 11:11:31 UTC

If I can build the SOA platform - I can create integration tests - one of the integration tests can then cover JBPM-1395

Comment 3 Thomas Diesler 2009-02-11 11:13:40 UTC

Link: Added: This issue is a dependency of JBPM-1395

Comment 7 Julian Coleman 2009-03-12 16:34:13 UTC

Link: Added: This issue depends JBQA-2139

Comment 9 Julian Coleman 2009-06-10 10:35:55 UTC

We now use anonymous SVN for the project checkouts.  MVEL is no longer required for SVN.

Revision 3145 of:
  build-common.xml
  build.xml
  builders/drools/build.xml
  builders/esb/build.xml
  builders/jbpm/build.xml
  builders/soa/opensso/build.xml
  builders/soa/p-consoles/build.xml
  builders/soa/p-consoles/jbpm/build.xml
  dependencies.properties

Commit message:
  Add new top-level build-common.xml to hold common routines.
  Move SVN handling into build-common.xml.
  Stop using mvel fragments to determine if we need to checkout or update.
  Use anonsvn for project checkouts.