Bug 779911 (SOA-2271)

Summary:	Need to work out format of EDS (teiid and modeshape) zip for separate deployment kit
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	trev <tkirby>
Component:	Build Process, EDS	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.ER1
Target Milestone:	---
Target Release:	5.1.0.ER3
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2271
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-04 19:59:09 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:
Bug Depends On:	779888, 779909, 779916, 779922, 779943, 779944, 779945, 779946, 779947, 779966
Bug Blocks:

Description trev 2010-09-07 14:46:15 UTC

project_key: SOA

Can you indicate which changes  need to be made to  the modeshape and teiid directories and any other changes we need to make and then re-assign the task back to me please

Comment 1 Ken Johnson 2010-09-10 20:02:20 UTC

Van and I discussed briefly today.  The build should produce two zips:
a) SOA-P zip (containing everything except Teiid and Modeshape)
b) EDS zip (containing both Teiid and ModeShape)

When the EDS zip is extracted, it should create an EDS subdirectory under the root SOA P directory.  This would be a peer to the jboss-as directory.  Within EDS will be a teiid directory (with the teiid files), a modeshape directory (with the modeshape files) and a build script that will install both teiid and modeshape into the target profile(s).

Comment 2 Van Halbert 2010-09-16 17:46:26 UTC

boss-as-p.5
        -	jboss-as
        -	seam
        -	resteasy
        -	....
        -	eds
                -	build.xml       -  running this will install, both, teiid and modeshape, with an option to install cxf

                -	teiid
                       -	build.xml   -  will only install teiid, with option to install cxf
                       -	resources
                               -	teiid-dataservices.zip  (deployment artifacts) - name of artifact is still being considered
                        -	examples
                        -	adminshell
                        -	client
                               -	teiid-client.jar

                -	modeshape
                        -	build.xml	- will only install modeshape
                        -	client
                               -	modeshape-client.jar   (same jar that should be in JBDS for the modeshape plugin)
                        -	resources
                                -	modeshape-dataservices.zip   (deployment artifacts)  - name of artifact is still being considered
                        -	examples

Comment 3 Van Halbert 2010-09-16 20:09:12 UTC

Talked with Ken,   the name of the teiid and modeshape zip's will be changed to:

-  teiid-runtime.zip
-  modeshape-runtime.zip

Comment 4 Julian Coleman 2010-09-17 12:57:12 UTC

Changes to the SOA assembly resolved with revision 6706 of:
  build-tools/build.xml
  build-tools/pom.xml

Commit message:
  SOA-2271
  Move the top-level "teiid" and "modeshape" directories out from
  "soa-p-<version>.zip" into a new "eds-<version>.zip".

Comment 5 Julian Coleman 2010-09-24 13:58:06 UTC

SOA assembly changed to make the top-level directory name for the EDS
zip file "eds" in revision 6807 of:
  build-tools/build.xml

Commit message:
  SOA-2271
  The top-level directory name for the EDS zip is "eds".

Comment 6 Van Halbert 2010-10-07 13:43:04 UTC

The task of working out the EDS structure, separate zips and associated tasks have been completed.   Any new problems should have a new jira created.

Comment 7 Van Halbert 2011-02-04 19:59:09 UTC

The deployment structure for Teiid and ModeShape has been completed and has been in testing for several ER release.s