WildflyBuildStreamTest and EapXpBuildStreamTest.java should also verify Bootable JAR application provisioning.
We could:
-
refactor the Bootable JAR and the trimmed server application variants into a unique one - when they're equivalent and only the provisioning method changes - that configures two different executions of the wildfly-maven-plugin, i.e. one that generates the trimmed server and one that generates the bootable JAR.
-
Add methods to ApplicationProvider (i.e. *ServerPath, as we do for other applications that generate the trimmed server) to expose the path of the provisioned Bootable JAR server directory, which is generated as an intermediate step of the Bootable JAR provisioning process in the target folder. This method can then be used by the aforementioned tests.
WildflyBuildStreamTest and EapXpBuildStreamTest.java should also verify Bootable JAR application provisioning.
We could:
refactor the Bootable JAR and the trimmed server application variants into a unique one - when they're equivalent and only the provisioning method changes - that configures two different executions of the
wildfly-maven-plugin, i.e. one that generates the trimmed server and one that generates the bootable JAR.Add methods to ApplicationProvider (i.e. *ServerPath, as we do for other applications that generate the trimmed server) to expose the path of the provisioned Bootable JAR server directory, which is generated as an intermediate step of the Bootable JAR provisioning process in the
targetfolder. This method can then be used by the aforementioned tests.