I am working on re-enabling the `hibernate-orm-modules` module but am
running into a problem being able to resolve Antlr 4 classes. I'm sure the
problem is related to the entry `` in
`hibernate-core.xml` but I am not sure how to fix that. Any ideas?
On Wed, Mar 11, 2020 at 9:49 AM Sanne Grinovero wrote:
> I'm not a fan of bytecode hacks either, so maybe let's just see what a POC
> looks like before tearing it down?
>
>>
I totally miss why we would want to even work on a POC given how much we
have on our shoulders? Could someone explain it
On Wed, 11 Mar 2020 at 12:16, Yoann Rodiere 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
When y'all talk about the bytecode enhancement solution, I'd like to better
understand what you mean exactly.
Do you mean at run-time like we did for ORM when we combined
Session/EntityManager? The problem there is that this only works when we
control the environment (WildFly e.g.). Do you mean
On Wed, 11 Mar 2020 at 08:39, Yoann Rodiere 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
> 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
