I’m currently reviewing the proposal  of WFLY-14934  feature request
and I’m struggling to understand what are the objectives of this feature.
The “Relevant Installation Types” section with selected “OpenShift s2i” in
the proposal  suggest this feature is OpenShift focused. However the
only differences between this new feature and existing bootable JAR can be
observed on bare metal. On bare metal this feature brings the same features
as bootable JAR does but it adds three things: persistent configuration,
multiple deployments and direct access to each file of the provisioned
server. In S2I scenarios there seems to be no difference between bootable
JAR and this feature. Form of the server in the application image is as far
as I know transparent for the user.
What are the real use-case scenarios of this feature?
 https://issues.redhat.com/browse/WFLY-14934 and
Jan (Honza) Kasik
Quality Engineer, EAP QE
Please note that we are currently running with significantly reduced CI
capacity, due to a hardware issue, which may go on for some time. Please be
mindful of the demand you put on CI. Avoid doing full retests when
re-running one or two jobs will do, avoid retests for unrelated failures,
avoid low priority PRs, avoid using CI for draft PRs.
It has been almost 4 weeks since the WF24 release, thus it is time to
plan a 24.0.1 micro release.
The current plan is to tag the release on July 22 and make it
available for download the following day.
If there are critical/blocker fixes that should target 24.0.1, please
ensure the appropriate JIRAs and pull requests are filed/submitted as
soon as possible, and reply to this thread to raise awareness.
Ideally, everything targeting 24.x should be ready for merge by next
Monday (the 19th). Anything affecting wildfly-core (16.x) should be
ready for merge by Thursday (the 15th).