WildFly 10 (our current version) is known not to work with Java 11. It (and several other Java apps) used a coding technique having to do with reflection and support for this was dropped in Java 10, causing errors. I've seen reports that this was corrected in WildFly 16, but I haven't tested that myself. However, WildFly has released 20.0.0.1, so we may as well upgrade to that.
Well we shouldn't update to 20 if it requires Java 12 as you said in Bug 27165, but we need to update it to something that works with Java 11.
CC: (none) => mageiaAssignee: bugsquad => javaSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=27165
(In reply to David Walser from comment #1) > Well we shouldn't update to 20 if it requires Java 12 as you said in Bug > 27165, but we need to update it to something that works with Java 11. Well, that's not correct. In that bug I originally mentioned Java 12 because I had it available for some previous testing, but I later amended the bug to say that the same results were obtained with Java 11. I've since confirmed that the warnings/errors concerning the reflection coding techniques have been corrected with WildFly 20 running both with the server running under Java 11 and a client built against Java 11 and the WildFly 20 client packages.
we will remove wildfly from cauldron.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED