[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ee4j-community] Status of JPA migration
- From: Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>
- Date: Sat, 7 Apr 2018 11:54:54 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
On 4/7/18 11:13 AM, Jens Schauder wrote:
I find it confusing that the status page
https://www.eclipse.org/ee4j/status.php doesn't mention JPA.
It has a row for EclipseLink, but that is AFAIK only the reference
AFAIK in case of JPA there has been no standalone spec-provided API for
quite long time with reasoning behind that that "the API is
implementation specific and should be provided by vendors/spec
implementations" - in case of EclipseLink the repo with API is one of
the repositories managed by eclipselink project.
Or is the specification and the TCK now part of EclipseLink?
I believe that it has been clearly communicated by others that specs and
TCK's as such are being/will be handled separately; these have never
been part of EclipseLink, nor managed by it.
Could someone shed some light on this?
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit