Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes Date of First Response: 2008-08-15 06:03:43 project_key: SOA
Link: Added: This issue is a dependency of SOA-674
Link: Removed: This issue is a dependency of SOA-674
Link: Added: This issue is incorporated by SOA-674
The top-level build.xml for the schemas both for the embedded and for the standalone versions are very similar and should be merged (build-tools/resource/schema/tool/e*/build.xml in the SOA source). The new functionality of asking the user for the profile to use should be conditionally applied if the relevant property is not set in build.properties. For the standalone version, the build.properties should set the property to "default". For the embedded version, the property should be commented out. The same property name should be used for both. This change should be documented in the release notes, as this will be a change from 4.2.
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Fixed in revision 1687 of build-tools/resource/schema/tool/e*/build* Log message: Use a single copy of the build.xml. Adjust the build.properties to suit.
Something like the following text should be added to the release notes. The schema (database configuration) tool uses the `org.jboss.esb.server.config' property to determine which server deployment to modify. For the standalone server, this is set to `default' in the 'build.properties' file. For the embedded server, there is no default, so the tool will ask the user for the name of the deployment . It is also possible to specify the deployment on the command lien, e.g. `ant -Dorg.jboss.esb.server.config=production`
Verified in IR4