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.