[hibernate-dev] Jakarta EE: JPA 3.0 is coming

[Sanne Grinovero]

On Wed, 11 Mar 2020 at 12:16, Yoann Rodiere <yoann at hibernate.org> wrote:
>
> > Yet I'm convinced that having a release
> > which provides full JPA 3.0 TCK between 5 and 6 (or however it gets
> > renamed) would be no good to us, as it would create an adoption
> > barrier for both cathegories of people: the ones not interested to
> > migrate away from JPA2, and the ones not interested to migrate beyond
> > JPA3.
>
> I get that, but I'm definitely not as hopeful as you are as to the reliability of those bytecode hacks you mentioned. But I guess that's an uphill battle.

I hear you: I'll make sure to focus on reading the mapping
(annotations) can be done as an independent PR and POC; not planning
to use any bytecode hacks for that.

I believe the mapping is actually the most important aspect: we can
drop the others, or iterate on such aspects later if we feel like we
need more.

Regarding on ORM7, ORM8 ... I remember talking about such options with
Steve and I believe he was open to it but we both agreed it's a last
resort choice, so let's hope that won't be necessary.

Thanks,
Sanne


>
> What's to stop us from supporting JPA2.0 in ORM 7, with the same hacks you mentioned for JPA3?
>
> People who want JPA3 only have a hack-free ORM 7 that happens to support JPA2 annotations.
> People who want JPA2 can migrate to ORM 7, and we'll provide hacks to make it work.
>
> At least we wouldn't be penalizing people who want to migrate to JPA3 with potentially unreliable bytecode hacks. Only people who want the latest and greatest on an older API (which is, after all, quite an unreasonable request) would have to put up with that.
> And we'll be clear about the fact that this is a major version, since we're switching to different APIs by default and will ultimately remove the old ones.
> And we'll be able to completely ignore these hacks in ORM 8 after we rebased it on 7, since ORM 8 will drop support for JPA2 (I hope?).
>
> Yoann Rodière
> Hibernate Team
> yoann at hibernate.org
>
>
> On Wed, 11 Mar 2020 at 00:17, Guillaume Smet <guillaume.smet at gmail.com> wrote:
>>
>> On Tue, Mar 10, 2020 at 7:12 PM Sanne Grinovero <sanne at hibernate.org> wrote:
>>
>> > The "big bang" approach that Validator implemented is an option as
>> > well; but the context is a bit different as we're having an actual
>> > major release being developed, and the matter of possible time
>> > pressure.
>> >
>>
>> Thus the proposal of Yoann and me to just rename the current 6 to a later
>> version and release a new major version that only contains the Jakarta
>> package change.
>>
>> That way, we don't end up doing additional work and having weird versions
>> partially supporting both.
>>
>> --
>> Guillaume
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>