Skip to main content

OJDeploy revisited libraries not included in compile via ant

My ojdeploy build was crashing when running via ant.
The difference between the command line build which was working and the ant build was a relative (../) location in the name of the workspace.

C:/Projects/Common/Model/../Common.jws instead of C:/Projects/Common/Common.jws

So the fix was as follows:
Add a new property with the location attribute:


And use this in my ant task:


  <taskdef name="ojdeploy"
    classname="oracle.jdeveloper.deploy.ant.OJDeployAntTask"
    uri="oraclelib:OJDeployAntTask"
    classpath="${ant.library}"/>
    <ora:ojdeploy xmlns:ora="oraclelib:OJDeployAntTask" 
    executable="${ojdeploy.path}"
    ora:statuslog="${basedir}/${ora.jdev.dir}${project.deploy.name}-ojd-stlog.xml"
    ora:buildscript="${basedir}/${oracle.jdev.dir}/ojd-build.xml">
      <ora:deploy>
        <ora:parameter name="workspace"
                       value="${workspace.fixed.location}"/>
        <ora:parameter name="project" value="${project.name}"/>
        <ora:parameter name="profile" value="${project.name}Deploy"/>
        <ora:parameter name="nodatasources" value="true"/>
        <ora:parameter name="forcerewrite" value="true"/>
    <ora:parameter name="basedir" value="${basedir}"/>
  </ora:deploy>
</ora:ojdeploy>

Comments

Popular posts from this blog

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop...

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]