Hide Forgot
++ 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"/>
Link: Added: This issue is related to SOA-376
Link: Added: This issue is related to SOA-1119
Link: Added: This issue related BRMS-27
All JEMS-EULA references look to have been replaced. Neil
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?
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.
Link: Added: This issue is related to SOA-1890
Link: Added: This issue is related to SOA-1109
Verified in CR1 build for 5.0