This is on JDeveloper 184.108.40.206. YMMV
- ojdeploy does not understand “nocompile=false”
If you have the nocompile property set, then ojdeploy does not compile your project no matter what the value of the property.
- ojdeploy does not like relative paths in the properties
For e.g., my workspace path was getting constructed as “C:\folder\build\..\MyApp\MyApp.jws”. That didn’t work – ojdeploy did not create the task-flow-registry file. I had to make sure that the workspace path was “C:\folder\MyApp\MyApp.jws”
- Chris Muir reports on OTN that there is a bug cos of which ojdeploy is case-sensitive to Windows paths as well. http://forums.oracle.com/forums/thread.jspa?messageID=9119712#9119712. Come to think of it, this could’ve been the root cause for my point 2 failure.