Fixes are available
Closed as program error.
Abstract: Attempts to run a Dojo custom build where the default profile location was changed to an alternate directory resulted in error(344). Problem: You create a Dojo custom build: 1. right click on Dojo project ? new ? Dojo custom build 2. changed the default profile location 3. click finish The custom build failed with the following error: Launching... error(344) File does not exist. profile: C:/Users/IBM_ADMIN/workspace/MyDojoTest/WebContent/dojo/util/bui ldscripts/js/standard.profile.js errors on command line; terminating application. Local fix: The Dojo custom build can be invoked from command line from within '?Your Project?\...\util\buildscripts' as follow: build.bat -p ../../../release.profile.js -r
The custom dojo build wizard made assumptions as to profile location. Prior to Dojo 1.7 the profiles had to be located in the buildscripts/profiles/ directory. The Dojo builder changed dramatically in Dojo 1.7 and this was no longer a restriction. The Dojo custom build wizard needed to be updated to support the Dojo 1.7+ builder.
The Dojo custom build wizard needed to be updated to support the Dojo 1.7+ builder. The fix for this APAR is included in Rational Application Developer v8.5.5.
Reported component name
WAS DEVTOOLS EC
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
WAS DEVTOOLS EC
Fixed component ID
Applicable component levels