Hide Forgot
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"/>
Link: Added: This issue is related to SOA-376
Link: Added: This issue is a dependency of BRMS-27
Link: Added: This issue related BRMS-27
Link: Removed: This issue is a dependency of BRMS-27
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
Link: Added: This issue is related to SOA-1119
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.
Link: Added: This issue depends JBESB-2280
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.
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>
Link: Added: This issue related SOA-1123