Is there a way we can make this work with wildfly-cloud-feature-pack?
It seems like this new FP and the existing one share a lot of overlap, but
then beyond the shared stuff for bootable jar a bit more stuff is needed
and for the s2i use case a bunch of incorrect-for-bootable jar stuff is
installed.
That kind of feels like layers.
To be fair, providing 1 feature pack and asking users to configure it for
the desired target might be more of a burden to them than providing 2 FPs.
But two FPs does seem confusing. It also increases our cost of delivery.
This is a bit of a tangent, but for sure we are going to need to adapt
Galleon so a FP can base on one of a set of compatible alternatives, not be
fixed to one. Dual mode for EE 10 and 11 will mean different flavors of
wildfly-ee, and we can't have that result in needing 2 of every other FP we
produce.
On Wed, Jul 30, 2025 at 10:16 AM Jean Francois Denise via wildfly-dev <
wildfly-dev(a)lists.jboss.org> wrote:
Hi,
I’ve created a proposal[1] to package a WildFly Bootable JAR for the
cloud when using the WildFly Maven Plugin (we are currently packaging a
bootable JAR for bare-metal only).
I’m looking for a feature team to work on this proposal.
I would also need an outside perspective to fully form the team.
Best regards,
JF
[1]
https://github.com/wildfly/wildfly-proposals/pull/748
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement:
https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
--
Brian Stansberry
Architect, JBoss EAP
WildFly Project Lead
He/Him/His