Hide Forgot
Complexity: Low Date of First Response: 2008-11-06 06:43:26 project_key: SOA See linked issue.
Link: Added: This issue depends JBESB-1723
Link: Added: This issue is related to SOA-546
Can we have confirmation that fixes are in place for 4.2CP03.
Link: Removed: This issue depends JBESB-1723
Link: Added: This issue depends JBESB-2171
Apologies, I closed this assuming you were referring to the ESB version but I suspect that is not the case. Not sure why the previous one was linked into ESB as it looks like SOA have (correctly) overridden the version.
Link: Removed: This issue depends JBESB-2171
Check with Kev to see if this is done against the 4.2.1CP branch in ESB.
This should be handled as part of the SOA build. We have a property in our build scripts, called version, that can be overridden to specify the appropriate release.
The name and version are set in the ESB product/build.xml: <!-- JBoss ESB version --> <property name="version" value="4.2.1CP3"/> <property name="esb.server.name" value="jbossesb-server-${version}"/> and in the SOA build-tools/dependencies.properties: ## ## ESB Build Settings Here ## soa_esb_jboss_server_name=jbossesb-server-4.2.1CP3 For SOA 4.2.0 CP03, these will be synchronised manually (4.2.1CP4).
Fixed in revision 2335 of: build-tools/dependencies.properties Commit message: Update ESB version for SOA 4.2.0 CP03. Update the ESB server name for ESB 4.2.1 CP4 (Fixes JIRA SOA-854).
Verified in CR5