[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Status of JPA migration
|
I kindly ask the PMC to create a pure JPA API project under the hood of
EE4J, separated from EclipseLink's implementation, and make EclipseLink
dependend of that. :-)
-Markus
-----Original Message-----
From: ee4j-community-bounces@xxxxxxxxxxx
[mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Lukas Jungmann
Sent: Samstag, 7. April 2018 17:11
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] Status of JPA migration
On 4/7/18 2:30 PM, Ivar Grimstad wrote:
>
>
> On Sat, Apr 7, 2018 at 11:55 AM Lukas Jungmann
> <lukas.jungmann@xxxxxxxxxx <mailto:lukas.jungmann@xxxxxxxxxx>> wrote:
>
> Hi,
>
> On 4/7/18 11:13 AM, Jens Schauder wrote:
> > Hi,
> >
> > 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
> > implementation.
>
> 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.
well, that is a _spec project_ (=specification related) whose only purpose
in the past was to provide issue tracker and mailing list for EG. What I was
referring to is http://git.eclipse.org/c/eclipselink/javax.persistence.git/
which is the repository containing JPA API sources relevant for EclipseLink
project.
thanks,
--lukas
>
>
>
> > 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.
>
> thanks,
> --lukas
>
> >
> > Could someone shed some light on this?
> >
> > Thanks
> > Jens
> >
> >
> > _______________________________________________
> > ee4j-community mailing list
> > ee4j-community@xxxxxxxxxxx <mailto:ee4j-community@xxxxxxxxxxx>
> > To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> >
> _______________________________________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx <mailto:ee4j-community@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-community
>
> --
>
> Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader
>
>
>
> _______________________________________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-community
>
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community