On Tue, Mar 10, 2020 at 7:12 PM Sanne Grinovero 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
I didn't mean to suggest that we fully implement both JPA 3.x and JPA
2.y in any one version.
I'm really just focusing on those principles I mentioned; the main ones being:
- don't spend ages on this effort
- don't add pressure on ORM 6
- not getting in the way of eventual ORM6 adoption
What
I'm curious... why are we saying that we need to simultaneously support
both sets of annotations and config settings?
As a user, if I choose to use the Jakarta-based JPA I would fully expect
that to only work with the Jakarta-based annotations and settings.
Is there something in the spec I am
Hi,
On Tue, Mar 10, 2020 at 2:48 PM Yoann Rodiere wrote:
> > In particular I wonder, how would you all feel if (for example)
> > Hibernate ORM 5.5.x were to depend on both JPA 2 and JPA 3 API
> > artifacts?
>
> Mixed feelings, to be honest
Same here. I thought we decided against supporting
Hello,
> In particular I wonder, how would you all feel if (for example)
> Hibernate ORM 5.5.x were to depend on both JPA 2 and JPA 3 API
> artifacts?
Mixed feelings, to be honest:
- It feels there's a high chance we'll waste our time on something
nobody needs. Who in their right mind
Hey,
I guess it should be doable to have a dependency on and implement both
APIs but I'm afraid you can't do that with plain Java, you need a build
tool to introduce these bridge methods with possible conversions.
I have been using the following tool in the past to support multiple
versions
Hi Christian,
On Tue, 10 Mar 2020 at 11:33, Christian Beikov
wrote:
>
> Hey,
>
> do you think it is feasible to create a separate artifact that is a
> bytecode rewriting of the main artifact, replacing javax.persistence by
> jakarta.persistence. This should be no big deal as e.g. the Maven Shade
Hey,
do you think it is feasible to create a separate artifact that is a
bytecode rewriting of the main artifact, replacing javax.persistence by
jakarta.persistence. This should be no big deal as e.g. the Maven Shade
Plugin does that as well. We would only need to accept additonal
poperties
Hi all,
as a consequence of having moved all Java EE technologies to the
Jakarta EE project at the Eclipse foundation, the API needs to change
so to address the Oracle trademark requirements.
The new JPA project lives here:
- https://github.com/eclipse-ee4j/jpa-api
For context, to make it
