Does you answer imply that this project will definitively be transferred to the EF? Then I'd like to propose that the status page is updated now so at least people see what will come in future. :-)
From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Ivar Grimstad
Sent: Samstag, 7. April 2018 14:31
To: EE4J community discussions
Subject: Re: [ee4j-community] Status of JPA migration
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.
Well, that's not entirely correct. There is a JPA API (https://github.com/javaee/jpa-spec), but it has not been transferred to Eclipse yet. I guess that is why it is missing from the list. As soon as the project has been created, it will appear there.
> 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
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader