Moving WildFly Elytron to Java 17
by Darran Lofthouse
Now that WildFly Core is built for Java 17 I would like to move WildFly
Elytron to Java 17 as well from our next releases for WildFly (2.7.x +).
Would this cause any issues for other projects that depend on WildFly
Elytron?
It should not affect Undertow as we use the Elytron Web project for
integration, maybe JBoss Remoting but also others with an Elytron
dependency so let me know if this would be an issue for your project.
--
Darran Lofthouse
Red Hat <https://www.redhat.com/>
darran.lofthouse(a)jboss.com
<https://www.redhat.com/>
2 months, 1 week
Use of the 'org.wildfly' groupId
by Brian Stansberry
Currently we have a number of different repos publishing artifacts using
the 'org.wildfly' groupId with no further namespacing.
Going forward I don't think we should allow any other new repos to do that.
It leads to administrative hassles, e.g. with setting things up in Nexus.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
4 months, 1 week
