ojdeploy ant task pitfalls

person Bijeshfolder_openJDeveloperlocal_offeraccess_time November 4, 2010

This is on JDeveloper YMMV

  1. 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.

  2. 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”

  3. 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.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>