Bug 778648

Summary: EULA file name and contents should match http://www.redhat.com/licenses/jboss_eula.html (html or text) - this will require quickstart and tooling build.xml file changes
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Julian Coleman <jcoleman>
Component: DistributionAssignee: Jeff Yu <cyu>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0CC: kconner
Target Milestone: ---   
Target Release: 5.0.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1123
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: SOA-1123 Environment:
Last Closed: 2010-02-11 14:31:27 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:

Description Julian Coleman 2009-01-13 14:21:11 UTC 
++ This bug is a clone of bug 778647 ++

Date of First Response: 2009-12-17 11:18:25
project_key: SOA

See SOA-376 for history

The SOA-P and BRMS product EULA file name and contents should be kept in synch with:  http://www.redhat.com/licenses/jboss_eula.html

And not the projects' EULA:  http://www.jboss.org/eula/

Note! The we cannot simply rename the file as the quickstarts - and other build.xml files depend on the JEMS-EULA.txt file being present in order to locate the product base dir - for example - in 4.2 CP03 CR5:

[ldimaggi@ldimaggi 42_CP03_CR5]$ grep -R EULA * | grep build

jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                     <available file="${product.dir}/JEMS-EULA.txt"/>
jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                     <available file="${product.dir}/JEMS-EULA.txt"/>
jboss-soa-p.4.2.0/jboss-as/tools/console/management/build.xml:                  <available file="${esb.root.dir}/JBossORG-EULA.txt"/>
jboss-soa-p.4.2.0/jboss-as/tools/console/management/build.xml:                  <available file="${esb.root.dir}/JEMS-EULA.txt"/>
jboss-soa-p-standalone.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                  <available file="${product.dir}/JEMS-EULA.txt"/>
jboss-soa-p-standalone.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                  <available file="${product.dir}/JEMS-EULA.txt"/>
jboss-soa-p-standalone.4.2.0/jboss-as/tools/console/management/build.xml:                       <available file="${esb.root.dir}/JBossORG-EULA.txt"/>
jboss-soa-p-standalone.4.2.0/jboss-as/tools/console/management/build.xml:                       <available file="${esb.root.dir}/JEMS-EULA.txt"/>
Comment 1 Julian Coleman 2009-01-13 14:21:11 UTC 
Link: Added: This issue is related to SOA-376
Comment 2 Julian Coleman 2009-01-13 14:21:11 UTC 
Link: Added: This issue is related to SOA-1119
Comment 3 Julian Coleman 2009-01-13 14:21:11 UTC 
Link: Added: This issue related BRMS-27
Comment 4 nwallace 2009-12-17 16:18:25 UTC 
All JEMS-EULA references look to have been replaced. Neil
Comment 5 Len DiMaggio 2010-02-08 20:25:24 UTC 
This has not been an issue for SOA-P 5.0:

grep -ir EULA * 
conf/base-build.xml:                    <available file="${product.dir}/JBossEULA.txt"/>
conf/base-build.xml:                    <available file="${product.dir}/JBossEULA.txt"/>

Was this change made for the 4.2 product stream?
Comment 6 nwallace 2010-02-09 21:03:25 UTC 
Looking in 4.2 there's no sign of any other EULA files and only one check for the existence of JBossOrg-EULA.txt in the management tool which seems to be in a 'or' anyway, the other side of which is the JBossEULA.txt.
Comment 7 Len DiMaggio 2010-02-11 14:31:05 UTC 
Link: Added: This issue is related to SOA-1890
Comment 8 Len DiMaggio 2010-02-11 14:31:05 UTC 
Link: Added: This issue is related to SOA-1109
Comment 9 Len DiMaggio 2010-02-11 14:31:27 UTC 
Verified in CR1 build for 5.0