×

Status message

This proposal has been approved and the Eclipse Project for JPA project has been created.

Eclipse Project for JPA

Basics
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Background: 

This project is created as part of the process of transitioning Oracle Java EE 8 and GlassFish technologies to the Eclipse Foundation as described in The Eclipse Enterprise for Java Project Top Level Project Charter.

Scope: 

Eclipse Project for JPA provides the API and TCK for Java Persistence starting from the specification defined by JSR-338.

Description: 

The Java Persistence API is the Java API for the management of persistence and object/relational mapping in Jakarta EE and Java SE environments. 

Why Here?: 

The top level EE4J project was created consistent with the direction described in The Eclipse Enterprise for Java Project Top Level Project Charter. This project is created under the top level EE4J project as one of Oracle Java EE 8 and GlassFish technologies being transitioned to the Eclipse Foundation.

People
Source Code
Source Repository Type: 
Eliana Hermione's picture

However if you're working in a true multi-user team environment you should not place your Eclipse-related files under svn control. Just think about what that means on a team where individuals are setting configuration aspects of their IDE and projects differently - if you revert or update you get whatever the last team member committed as HIS/HER config settings. If another team member reverts or updates well you get the ideal British essay writers Uk.