EclipseLink/Building

Licensing Issues

We are still sorting through some licensing issues for some of the libraries we depend on and upgrading code to use libraries that are EPL compliant. In the mean time, you may be able to use the following information to build the various projects.

SVN Structure

At the moment, all code can be found in the org.eclipse.persistence/trunk directory on the technology SVN server. The following directories are designed to be compilable sub-components of EclipseLink. They each contain an src directory and potentially a resource directory that the files necessary for building and running.

Runtime

• foundation/core - the core of EclipseLink
• foundation/extension.oracle - extensions that require Oracle-specific libraries for compilation. You will not be able to build these extensions until some of the licensing issues have been sorted out. The compiled classes will be checked in soon so that people without those dependancies can use the compiled classes.
• jpa/core - EclipseLink's JPA support
• foundation/core.lib - this will contain all the libraries the core depends on to build.

Testing

• foundation/core.test - the core testing for EclipseLink
• foundation/extension.oracle.test - the testing for EclipseLink's Oracle-specific functionality. Like the extension.oracle directory, this will only build after some licensing issues have been sorted out.
• jpa/core.test - the JPA tests for EclipseLink

Projects and Dependancies

Eclipse Projects are available for foundation/core, foundation/core.lib, foundation/core.test jpa/core and jpa/core.test. These projects should allow you to use most of the core EclipseLink functionality.

Until our dependancies have been checked in, you should be able to build use the following dependancies to build.

1. foundation/core depends on the following:
   1. foundation/core.lib - The Eclipse Project defined in this folder
   2. Eclipse Variable JAVAEE_LIB - this should point to javaee.jar which is included with Sun's JavaEE SDK that can be downloaded from the Sun website.
2. jpa/core depends on the following:
   1. foundation/core - The Eclipse project defined in this folder
   2. Eclipse Variable ANT_LIB that points to the ANT. You can point the the ANT Eclipse plug-in. We are using: ECLIPSE_HOME/plugins/org.apache.ant_1.6.5/lib/ant.jar
3. foundation/core.test should have all its dependancies already set but provides an ant build that sets up some xml files to run
4. jpa/core.test should have all its dependanciees already set but provides an ant build to build persistence units for testing
5. foundation/extension.oracle depends on a selection of jars from Oracle products. In order to build this project you will need to obtain all these jars. As a result the class files from this project are checked in so they can be used by people that do not have those jars
   1. Jars:
      1. aqapi.jar - Oracle Advanced Queue
      2. sdoapi.jar - Oracle Spatial API
      3. dms.jar - Oracle management
      4. An oracle JDBC driver
      5. xdb.jar - XDB
      6. xml.jar - Oracle XML support
      7. xmlparserv2.jar - Oracle XML parser
   2. Projects
      1. foundation/core depends on the same jars as foundation/extension.oracle and as a result, it has also had class files checked in
6. foundation/extension.oracle.test depends on
   1. foundation/extension.oracle
   2. foundation/core.test
   3. jpa/core
   4. jpa/core.test

Port TODO List

List of task, items, issues, refactorig left to due from the initial port.

• Check-in dependent libraries and jars.
• Re-synch with MAIN (this will likely be done on a TX by TX basis by the people that merged those TXs since the last merge.)
• Antlr upgrade - rename done and tests now pass, CTS run still required
• Get build scripts working for each component.
• Get all tests passing. - JPA JUnit tests and legcacy LRG model currently pass
• SVN cleanup, remove some dead directories.
• Remove deprecated packages and classes.
• Move JAXB code to MOXy.
• Move EIS code and tests to EIS
• Move left-over internal classes to internal packages.
• Internationalization.
• Server tests.
• Performance tests.

How To

• Make changes to ANTLR generated JPA code