Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Building"

(Issues)
Line 38: Line 38:
  
 
We are currently in the middle of upgrading our ANTLR version.  Until the upgrade is complete, JPQL will not work.
 
We are currently in the middle of upgrading our ANTLR version.  Until the upgrade is complete, JPQL will not work.
 +
 +
== Port TODO List ==
 +
 +
List of task, items, issues, refactorig left to due from the initial port.
 +
* Check-in dependent libraries and jars.
 +
* Get build scripts working for each component.
 +
* 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.
 +
* Re-synch with MAIN.

Revision as of 10:56, 28 August 2007

Under Construction

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 and jpa/core. 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.
    3. Eclipse Variable ANTLR30_LIB - this should point to antlr-runtime-3.0.jar which is included in ANTLR 3.0 that can be downloaded from the ANTLR 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

Issues

We are currently in the middle of upgrading our ANTLR version. Until the upgrade is complete, JPQL will not work.

Port TODO List

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

  • Check-in dependent libraries and jars.
  • Get build scripts working for each component.
  • 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.
  • Re-synch with MAIN.

Back to the top