Require SE 17 compiler, compile to SE 11 source and target level
by Brian Stansberry
WDYT about doing in main what I did in the EE11 topic branch?
https://github.com/wildfly/wildfly/commit/af6e723a27228884dbc3acdc66be10c...
I did that in EE 11 because we know some EE 11 APIs or impls will require
SE 17. So we need the SE 17 compiler to build with those deps. But we want
our own (WFLY and WFCORE) code to remain SE 11 compatible. So the resulting
binary level must be SE 11 and no language features or SE APIs > 11 can be
used by our own code.
Trying to only do this in the EE11 branch has proven to be a pain, because
a bunch of things like github actions are using SE 11 to build and that
blows up when run against the EE11 branch.
If we did this I'd add a profile that could set the compiler version back
to 11. CI jobs that need to both build the server and run the testsuite on
11 could activate that profile.
Over the course of this year the SE 11 build and test use cases should
become the secondary cases, ones that need special handling Iike activating
a profile. SE 17 should become the 'default, it just works with no special
effort' case. Supporting both EE 10 and 11 in different feature packs is
one reason to keep SE 11 support around, but even with EE 10 our 'typical'
case should become SE 17, not SE 11.
Thoughts?
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
8 months, 3 weeks
Pushing back the WildFly 32 Beta Release by One Week
by Darran Lofthouse
In general everything is proceeding well with our preparations for the
WildFly 32 Beta release, however with the introduction of the WildFly
feature development process we have some work which is being completed.
It feels a shame that work which is almost ready will miss this Beta
release by strictly applying the time box and we would really like to get
the work we are doing into the hands of our community so we have decided we
will push the release back by one week so some remaining items can be
completed.
WildFly Core is already tagged and we are not planning a further WildFly
Core tag unless a blocking issue is identified, we would now be aiming to
tag WildFly 32 Beta on Wednesday the 3rd April so the release can be
published on Thursday the 4th April.
--
Darran Lofthouse
Red Hat <https://www.redhat.com/>
darran.lofthouse(a)jboss.com
<https://www.redhat.com/>
8 months, 4 weeks
WildFly Server Migration 1.12.0.Final released
by Eduardo Martins
Hi everyone, I’m quite happy to announce the availability of WildFly Server Migration Tool 1.12.0.Final, the latest release of the standalone tool that helps migrating between different versions of WildFly distributions.
This tool may be used to do the following server migrations:
* WildFly 14.0 to WildFly 26.0
* WildFly 15.0 to WildFly 26.0
* WildFly 16.0 to WildFly 26.0
* WildFly 17.0 to WildFly 26.0
* WildFly 18.0 to WildFly 26.0
* WildFly 19.0 to WildFly 26.0
* WildFly 20.0 to WildFly 26.0
* WildFly 21.0 to WildFly 26.0
* WildFly 22.0 to WildFly 26.0
* WildFly 23.0 to WildFly 26.0
* WildFly 24.0 to WildFly 26.0
* WildFly 25.0 to WildFly 26.0
* WildFly 26.0 to WildFly 31.0
* WildFly 27.0 to WildFly 31.0
* WildFly 28.0 to WildFly 31.0
* WildFly 29.0 to WildFly 31.0
* WildFly 30.0 to WildFly 31.0
* JBoss EAP 7.0 to JBoss EAP 8.0
* JBoss EAP 7.1 to JBoss EAP 8.0
* JBoss EAP 7.2 to JBoss EAP 8.0
* JBoss EAP 7.3 to JBoss EAP 8.0
* JBoss EAP 7.4 to JBoss EAP 8.0
A couple of important notes:
* Due to a WildFly 31 issue it's not possible to migrate (using this tool) to such version, from WildFly 25.0 or older. To accomplish this a multiple step migration is needed, by first migrating to WildFly 26, and finally migrating from WildFly 26 to WildFly 31.
* Migration from a WildFly version before the legacy security framework's removal (WildFly 24 or older), to WildFly 26, changes all security configurations to WildFly 26 defaults, which means that further manual configuration should be needed in case the defaults were *not* previously being used.
For this particular release I would like to send a very special "thank you" to Ivo Studensky and Ondrej Kotek, for their outstanding contributions.
Please head to the release page on GitHub to download the tool:
https://github.com/wildfly/wildfly-server-migration/releases/tag/1.12.0.F...
To learn how to setup and use this tool, besides downloading and extracting the zip file attached to the release, please refer to the included User Guide, which may be found inside the docs/user-guide directory.
—E
9 months, 1 week
