Release Notes - WildFly Arquillian - Version 3.0.0.Final - HTML format

Feature Request

  • [WFARQ-3] - Option to set startup timeout
  • [WFARQ-65] - Add support for WildFly bootable JAR
  • [WFARQ-66] - Upgrade Arquillian from 1.4 to 1.6
  • [WFARQ-75] - Support --read-only-server-config configuration

Bug

  • [WFARQ-47] - Container#close always ends up in exception closing ManagementClient: NPE
  • [WFARQ-70] - Shutdown thread may destroy a wrong process in stopInternal method
  • [WFARQ-74] - The bootable JAR should not require the JBoss Home environment variable or property to be set
  • [WFARQ-78] - Custom containers are not stopped from a LoadableExtension
  • [WFARQ-79] - Do not capture System.out early for the console consumer
  • [WFARQ-83] - Connecting the management client will fail if the JMX subsystem is not present

Task

  • [WFARQ-53] - Migrate the provisioning for test servers to Galleon
  • [WFARQ-61] - Migrate Java EE components to Jakarta EE components
  • [WFARQ-67] - Update the GitHub Action to include the logs for failed runs
  • [WFARQ-68] - Upgrade the wildfly-maven-plugin from 2.0.0 to 2.0.2
  • [WFARQ-69] - Schedule a nightly CI job that runs against the latest WildFly upstream
  • [WFARQ-72] - Allow the project to be released with Java 11+
  • [WFARQ-73] - Do not provision servers if tests are skipped
  • [WFARQ-76] - Require a minimum Maven version of 3.6.0 for the build
  • [WFARQ-77] - Add a utility to test the minimum container version

Component Upgrade

  • [WFARQ-62] - Upgrade WildFly Core to 11.0.0.Final
  • [WFARQ-63] - Upgrade jboss-parent from 29 to 37
  • [WFARQ-64] - Upgrade wildfly-core from 13.0.0.Beta6 to 13.0.0.Final

Enhancement

  • [WFARQ-71] - Create a more common managed container

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.