Are JDev autogenerated paths needed to create ear, war and jar files ?

Question

Hi
We want to create ear, war and jar files from Ant build script generated from JDeveloper 11.1.1.7.
We also like to use ojdeploy with it.
In the process of creating build.xml files from projects, we see these paths.
We also have standalone Weblogic installed with ADF runtime 11.1.1.7
Questions:
1- Do we need these path ids to generate ear, jar, war files properly and then deploy the ear to our standalone Weblogic so that our webapp can run ok ?
2- Why are they generated, if they are not needed
From research, it appears that we don't need these paths except to keep ant targets of init, compile, exec etc with ojdeploy.
3- Is that true ?
We are afraid that because no paths are listed in the build.xml, then when we deploy the ear app, it cant use the ADF runtime on the standalone WLS.
Thanks in advance for answering.
Sincerely
eg of paths generated below:
  <path id="library.SOA.Designtime"/>
  <path id="library.SOA.Runtime"/>
  <path id="library.BPEL.Runtime"/>
  <path id="library.Mediator.Runtime"/>
  <path id="library.MDS.Runtime">
    <pathelement location="{oracle.middleware}/oracle_common/modules/oracle.mds_11.1.1/mdsrt.jar"/>
  </path>
  <path id="library.BC4J.Service.Runtime">
    <pathelement location="{oracle.middleware}/oracle_common/modules/oracle.adf.model_11.1.1/adfbcsvc.jar"/>
    <pathelement location="{oracle.middleware}/oracle_common/modules/oracle.adf.model_11.1.1/adfbcsvc-share.jar"/>
    <pathelement location="{oracle.middleware}/oracle_common/modules/commonj.sdo_2.1.0.jar"/>
    <pathelement location="{oracle.middleware}/modules/org.eclipse.persistence_1.1.0.0_2-1.jar"/>
    <pathelement location="{oracle.middleware}/oracle_common/modules/oracle.webservices_11.1.1/wsclient.jar"/>
    <pathelement location="{oracle.middleware}/oracle_common/modules/oracle.web-common_11.1.1.jar"/>
  </path>
  <path id="library.TopLink">
    <pathelement location="{oracle.middleware}/modules/com.oracle.toplink_1.0.0.0_11-1-1-5-0.jar"/>
    <pathelement location="{oracle.middleware}/modules/org.eclipse.persistence_1.1.0.0_2-1.jar"/>
    <pathelement location="{oracle.middleware}/modules/com.bea.core.antlr.runtime_2.7.7.jar"/>
    <pathelement location="{oracle.middleware}/modules/javax.persistence_1.0.0.0_2-0-0.jar"/>
  </path>
  <path id="library.Oracle.Rules"/>
  <path id="classpath">
    <path refid="library.SOA.Designtime"/>
    <path refid="library.SOA.Runtime"/>
    <path refid="library.BPEL.Runtime"/>
    <path refid="library.Mediator.Runtime"/>
    <path refid="library.MDS.Runtime"/>
    <path refid="library.BC4J.Service.Runtime"/>
    <path refid="library.TopLink"/>
    <path refid="library.Oracle.Rules"/>
  </path>

Answer 1

There are two different things here. Using ant to build the class files and then building an ear from the class files and other resources.
The building part needs the libraries if you use javac as compiler. Building an ear file only needs the path to the jar files which are packed into the ear.
In this sense you need the pages you see in the build.xml.
Then Jdev offers another way: ojdeploy. This tool is a Jdev without a gui.
You can use this tool and build the classes for each project of a workspace and to build build war and ear file. This is just like you click the rebuild button for each project and then the deploy the projects and application. If you use this approach you don't need the generated path ids as the whole build process is done inside Jdev as it's done on your developer pc.
Timo