Re: [hibernate-dev] Remove or disable the WildFly feature packs of Hibernate ORM?
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 only run a handful of
tests, not the whole test suite, and I expect the JPA 3 migration will
require extensive testing in WildFly's master branch anyway.
#2 looks pointless for 5.5 at the moment as JPA3 is unlikely to work in
older versions of WildFly (for the reasons you mentioned, and probably also
because of Jipijapa).
So, +1 to drop it for now. I assume you'll do the same for OSGi?
If we end up doing this, I'll do the same for Hibernate Search 5.12 (which
I haven't started yet - please ping me when you think it's worth working
on?)
As to the future... We've talked about running the whole (huge) test suite
in various environments, perhaps through Arquillian or some custom
framework. It looks like a lot of work, and I'm not sure we'll ever manage
to do that completely, but if we ever restore WildFly tests, I'd feel safer
if we go that route than just write a few tests targeting WildFly
specifically. Maybe at that point we'll have the testing framework already
in place and that will be easy? A man can dream :)
Yoann Rodière
Hibernate Team
yoann(a)hibernate.org
On Thu, 16 Apr 2020 at 00:03, Sanne Grinovero <sanne(a)hibernate.org> wrote:
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 yet.
I see several options:
A] I could disable the feature pack generation and its integration tests.
B] Keep generating and releasing a knowingly broken feature pack,
disable its integration tests, document this is work in progress.
C] Delete all this stuff
Frankly it's tempting to just delete it all: WildFly has switched to a
new model which replaces the "feature pack" notion we have, so even if
Wildfly were to provide an Jakarta EE 9 build for us to run
integration tests sometimes soon I'm sadly quite certain that we'll
have to rethink how these packs are generated, and if it's still worth
for us doing this.
Any thoughts?
Thanks,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev