Bug 778633 (SOA-1109)

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 4 Reporter: Len DiMaggio <ldimaggi>
Component: DistributionAssignee: Jeff Yu <cyu>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 GA, 4.2 CP03CC: kconner
Target Milestone: ---   
Target Release: 4.2 CP04   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1109
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-02 17:29:59 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 Len DiMaggio 2009-01-06 15:19:15 UTC
Date of First Response: 2009-01-09 08:28:06
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 Len DiMaggio 2009-01-06 15:19:27 UTC
Link: Added: This issue is related to SOA-376


Comment 2 Len DiMaggio 2009-01-06 15:24:39 UTC
Link: Added: This issue is a dependency of BRMS-27


Comment 3 Len DiMaggio 2009-01-06 15:40:56 UTC
Link: Added: This issue related BRMS-27


Comment 4 Len DiMaggio 2009-01-06 15:41:26 UTC
Link: Removed: This issue is a dependency of BRMS-27 


Comment 5 Julian Coleman 2009-01-09 13:28:06 UTC
The current EULA's have this minor difference from the downloadable version:

@@ -19,7 +19,7 @@
 License v.1, and, pursuant to the OASIS BPEL4WS standard, requires parties
 wishing to redistribute to enter various royalty-free patent licenses. Each of
 the foregoing licenses is available at
-www.opensource.org/licenses/alphabetical. The Programs are comprised of
+http://www.opensource.org/licenses/alphabetical. The Programs are comprised of
 hundreds of software components. With the exception of certain image files
 identified in Section 2 below, the license agreement for each software
 component is located in the software component's source code and permits User

This doesn't require a change to be made to 4.2.0 CP03.

In future, we need:
  a text version of the license to be available
  a mechanism for update notification


Comment 6 nwallace 2009-01-12 08:59:48 UTC
Link: Added: This issue is related to SOA-1119


Comment 7 Jeff Yu 2009-03-19 08:36:49 UTC
Need to make sure which JBossESB branch is the SOA-P 4.2CP04 depending on.

If it is from trunk, then this issue should already been fixed by Dan.

Comment 8 Jeff Yu 2009-03-19 08:36:49 UTC
Link: Added: This issue depends JBESB-2280


Comment 9 trev 2009-03-26 10:33:46 UTC
quickstart build file in the esb branch contains the check for JEMS-EULA,txt, if the file name is not changed then no further work is needed, the correct EULA will be overlayed.

Comment 10 Len DiMaggio 2009-06-02 17:29:59 UTC
Verified fixed in 4.2 CP03 CR4:

grep -ir EULA * | grep build 

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}/JBossEULA.txt"/>
jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                     <available file="${product.dir}/JBossEULA.txt"/>
jboss-soa-p.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                     <available file="${product.dir}/JBossEULA.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}/JBossEULA.txt"/>
jboss-soa-p-standalone.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                  <available file="${product.dir}/JBossEULA.txt"/>
jboss-soa-p-standalone.4.2.0/jboss-as/samples/quickstarts/conf/base-build.xml:                  <available file="${product.dir}/JBossEULA.txt"/>

References to JBossORG-EULA.txt is not an issue as the EULA is included in this ant <or> block:

        <!-- Are we embedded in a jbossesb distribution hierarchy? -->
        <condition property="hierarchy.jbossesb">
                <or>
                        <available file="${esb.root.dir}/JBossORG-EULA.txt"/>
                        <available file="${esb.root.dir}/JBossEULA.txt"/>
                </or>
        </condition>



Comment 11 Len DiMaggio 2010-02-11 14:31:05 UTC
Link: Added: This issue related SOA-1123