2014-Dec Status Report for the Apache OpenJPA Project == Summary == Apache OpenJPA is a persistent object management kernel for relational and non-relational databases. For relational database, OpenJPA provides persistence for Plain Old Java Object (POJO). OpenJPA is compliant to industry-standard Java Persistence Architecture (JPA) version 2.0 version and runs in stand-alone JSE as well as JEE containers and many other lightweight frameworks, such as Tomcat, TomEE, Spring or OSGi. == Community == OpenJPA developers had, over past several years, not only developed a general-purpose, stable software for complex Object-Relational Mapping but also ensured its stability across many released versions. OpenJPA has a solid user base and many have migrated their persistence provider to OpenJPA from more well-known provider in the past. Current OpenJPA developer/committers actively maintain the code base as well as support via the mailing list users and the code service streams. However, developer resource is shrinking as many senior committers are not active and new volunteers are hard to come by as new development opportunities are rare and hard to incorporate. Also lack of strong corporate interest/sponsorship is affecting future growth/expansion of the community. PMC members are exploring how to invigorate the project. We hope that the Board members may be able to share their experience on how to re-energize a matured project in its maintenance phase of life. == Recent Work == OpenJPA development team member Jody Grassel has upgraded Serp bytecode library to version 1.15 for Java 8 language features (e.g. lambda expression) and integrated OpenJPA with the upgrade. As OpenJPA natively uses bytecode enhancement, supporting Java 8 has more than usual impact on OpenJPA. Many requests have been received for upgrade to JPA 2.1 compliance. Prototype work for supporting JPA 2.1 features such as Store Procedure support has started. == Issues == One of the nightly builds (2.3.1) artifact is missing [1] in the repository. The issue is likely to be an infrastructure issue and is being tracked by [2] [1] https://repository.apache.org/snapshots/org/apache/openjpa/apache-openjpa/2.3.1-SNAPSHOT/ [2] https://issues.apache.org/jira/browse/OPENJPA-2537