Apache OpenJPA
Go to file
Enrico Olivelli c97bb58a35 hard code key cache 2020-07-17 18:04:50 +02:00
.github/workflows hard code key cache 2020-07-17 18:04:50 +02:00
openjpa [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-all [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-examples [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-features [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-integration [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-jdbc [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-jest [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-junit5 [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-kernel [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-kubernetes [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-lib [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-persistence [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-persistence-jdbc [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-persistence-locking [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-project [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-slice [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-tools [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
openjpa-xmlstore [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00
scripts OPENJPA-2747 upgrade to jpa-2.2 api 2019-03-27 12:29:57 +01:00
src OPENJPA-2753 add a profile for Oracle as Docker image 2019-01-06 23:43:41 +01:00
.gitignore [OPENJPA-2781] persistence_2_1.xsd is bundled for offline processing 2019-03-24 20:32:47 +07:00
LICENSE [OPENJPA-2781] persistence_2_1.xsd is bundled for offline processing 2019-03-24 20:32:47 +07:00
NOTICE upgrade license year to - 2015 2015-04-03 19:38:01 +00:00
README.adoc fix missing space in readme 2019-01-03 21:28:04 +01:00
patchoj.py [OPENJPA-2751] trailing white-spaces were removed 2018-10-02 12:32:32 +00:00
pom.xml [maven-release-plugin] prepare for next development iteration 2020-07-07 11:19:15 +02:00

README.adoc

= Apache OpenJPA - README

== Preface
Thank you for downloading this release of Apache OpenJPA.

Apache OpenJPA is an implementation of the Java Persistence API specification.


== License
The content of this repository is licensed under Apache License 2.0
http://www.apache.org/licenses/LICENSE-2.0

== Further Information

The following files can be found in the openjpa-project subdirectory:

* openjpa-project/BUILDING.txt
* openjpa-project/CHANGES.txt
* openjpa-project/RELEASE-NOTES.html

For documentation and project information, please visit our project site:
    http://openjpa.apache.org/


== Compiling

The best way to compile Apache OpenJPA yourself is to run the build against the default derby database.

 $> mvn clean install -Dsurefire.excludes.locking=**/*

== Testing against different Databases

The Apache OpenJPA project also contains a setup for testing against multiple databases.
The easiest way is to use Docker.
We assume that Docker is installed to be used from your current user.
The respective database image has to be started manually bofore starting the build.
The reason for not starting it as part of the build itself is to be able to look at the database content after the build did run.

To start e.g. a PostgreSQL Docker image you can simply invoke the following command.
Note the -N Maven option which stands for 'non-recursive'.
This is used because the docker container is configured only at the root project but not at his children.

 mvn -N -Ptest-mysql-docker docker:start

After that you can execute your tests with the respective Maven profile

 mvn clean install -Ptest-mysql-docker

Once the Docker image for the database is not needed any longer one can stop and remove it:

 mvn -N -Ptest-mysql-docker docker:stop
 mvn -N -Ptest-mysql-docker docker:remove


The following Maven profiles do exist so far:

* test-mysql-docker
* test-mariadb-docker
* test-postgresql-docker