Difference between revisions of "EclipseLink/Development/Testing/Prereq"

Revision as of 12:02, 7 January 2008

Summary

The EclipseLink test suites are written using JUnit. They consist of a set of jars and classes that contain various tests and resources. The tests are contained in the eclipselink.*.test projects. This page is intended to outline the setup and execution steps required to successfully run the JUnit tests. There are 2 ways to checkout EclipseLink and for each of these there are 2 ways to run tests.

1. Checkout using Subclipse all projects individually into your eclipse workspace
   1. Build classes in eclipse and run/debug there
   2. Build/run classes using Ant
2. Checkout using TortoiseSVN the root trunk into a folder outside your workspace (IE: c:/view_el) and either use ant to build an eclipselink.jar or create proxy projects using link to source from eclipse - Recommended if you would like to build the eclipselink.jar - but you will requires some build.properties changes.
   1. Build classes in eclipse and run/debug there
   2. Build/run classes using Ant

Prerequisites

• TortoiseSVN and a saved PuTTY SSH session
• TortoiseSVN - network setting - SSH client set as <TortoiseSVN_HOME>\bin\TortoisePlink -l <userName> -pw <password_cleartext>

• Eclipse 3.2|3.3|1.5 installed with the subclipse plug-in for in-eclipse checkouts
• Referenced core projects eclipselink.core and eclipselink.lib checked out into workspace or view
• Required projects for your specific view eclipselink.sdo|moxy|jpa|dbws, eclipselink.sdo|moxy|jpa|dbws.lib and eclipselink.sdo|moxy|jpa|dbws.test checked out into workspace or view
• If using Ant instead of Eclipse to run - edit build.properties either at this project level or better - globally override the following in your user directory on windows: C:/Documents and Settings/<user-dir>/build.properties

javaee.lib=<jar_location>/javaee.jar - required by MOXy or core tests
junit.lib=<JUNIT_HOME>/junit.jar 

• Override any project specific variables in your <user-dir>/build.properties depending on whether you are running inside an eclipse workspace or outside.

Classpath Variables

Ensure the following (Java | Build Path | Classpath Variables) are set:

• ORACLE_JDBC_LIB variable has been mapped to your database's JDBC driver (compile-time for extension project)
• JDBC_LIB variable has been mapped to your database's JDBC driver (vendor-agnostic driver)
• Some JDBC drivers may require the system library path to be set, or dlls to be on the path
• TOOLS_LIB variable has been mapped to your JDK tools.jar
• The following jars may be placed into extension.oracle.lib.external
  • AQAPI_LIB variable has been mapped to your aqapi*.jar
  • SPATIAL_LIB variable has been mapped to sdoapi.jar
  • XDB_LIB variable has been mapped to xdb.jar
  • XML_LIB variable has been mapped to xml.jar
  • XMLPARSERV2_LIB variable has been mapped to the oracle specific xmlparserv2.jar

How To

• General prerequisites for building & running EclipseLink tests
• Make changes to ANTLR generated JPA code
• Run the legacy LRG
• Run the JPA Junit tests
• Run the MOXy Junit tests
• Run the SDO Junit tests