On Wed, 15 Apr 2020 at 02:16, Gail Badner wrote:
>
> FWIW, there's no point in fixing HHH-13916 unless we hear that Infinispan is
> going to use the fix.
I suppose we can expect that that will eventually happen - I just
don't know when and were to best make a note of such a need? I'd say
if you
As we're working to upgrade to Jakarta EE 9, our feature packs for
Wildfly are not going to be functional for a while at least.
Not only do we have to upgrade to JPA 3, but we also need to upgrade
our integrations with a different Validator, a different CDI - none of
these are provided by WildFly
Hi Galder,
Thanks for the response. I agree this would be a good change for H6. I'm
happy to hear that this is on someone's radar for Infinispan.
Sanne, regarding:
> I'd say if you clearly mark the old method deprecated (or even remove
it?) it
will be guaranteed we don't forget about this improve
Hello,
As far as I know, the feature packs are here for two reasons:
1. To test compatibility of ORM with WildFly while still developing it.
2. To provide non-official (wrt. WildFly) ways to upgrade ORM to the latest
version within WildFly.
#1 does not look *that* important for 5.5, since we onl
