And one Wildlfy build failed apparently on network issue with Maven central:
Could not transfer artifact com.sun.activation:jakarta.activation:jar:1.2.2 from/to central (https://repo.maven.apache.org/maven2): /home/runner/.m2/repository/com/sun/activation/jakarta.activation/1.2.2/jakarta.activation-1.2.2.jar.part (No such file or directory)
Intermittent I would say.
All Liberty tests are failing because instead of the MicroProfile Starter landing index page, the app server displays some different context, it looks like some Liberty landing page.
Do we have theapp context URL right for Liberty?
@Emily-Jiang I am on the gradle testing now.
I am leaving Payara, Liberty and Helidon in and I am taking Tomee, Quarkus and Wildfly out of Gradle for the time being.
Tomee: I don't know how to add support for it. Will open an issue and ask.
Wildfly: I am not sure how to handle it the best way, I asked about it on Zulip: https://bit.ly/3gFteD2
Quarkus: I know how to do it, it's just me taking the time to do it, work in progress now...
We can release what works and then release updates as support for the aforementioned runtimes comes in.
Wildfly: We are in a talk with WildFly guys on how to do it. it turned out there is no straightforward way to use gradle to build a bootable jar, it's all Maven. They suggested an example for me on how to control the maven plugin from gradle task. I will be looking into it.
Quarkus: I am on it.
As far as I am concerned, we can release with Payara and Helidon groovy support now.
Liberty needs to be fixed.
And we can add the rest as it comes in patch releases.
Hello, tests passed, including gradle ones for Payara, Liberty and helidon, so this is O.K. to ack and merge: