Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Status of JPA migration

I really don't want to bother, but from the outside this all looks rather chaotic. I hope at least *someone* (even if nobody knows him) has a comprehensive list of *everything* that gets transferred to the EF, and about each project's actual status. ;-)

-Markus

 

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Ivar Grimstad
Sent: Samstag, 7. April 2018 14:55
To: EE4J community discussions
Subject: Re: [ee4j-community] Status of JPA migration

 

I am under the impression that all the Java EE 8 technologies will be transferred. And JPA is a part of Java EE 8, so I don't know why it shouldn't.

Regarding the status list, I think the project needs to be created (i.e. get a name) before it appears in the list...

 

Ivar

 

On Sat, Apr 7, 2018 at 2:51 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

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. :-)

-Markus

 

 

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 Sat, Apr 7, 2018 at 11:55 AM Lukas Jungmann <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.

 



> 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
> 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

--

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

--

Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader


Back to the top