wildfly-jar-maven-plugin
wildfly-jar-maven-plugin copied to clipboard
wildfly-extras
Extend Maven plugin to create bootable jar from existing Web Archive.
Please extend the wildfly-jar-maven-plugin plugin to allow generation of a bootable jar from an existing .war file. This will be prove very useful in those cases where web archive assembly is more complex and cannot be handled by maven directly.
I was thinking at a path to a war (or any supported deployment) file that would be used during packaging time, not a Maven "dependency". So a new option in the Maven plugin configuration.
This issue in some way is related to being able to build a Bootable JAR outside Maven, something like: java -jar wildfly-bootable-jar-builder.jar build --galleon-layers=x,y,z --location=org.wildfly:wildfly-galleon-feature-pack:24.0.0.Final --deployment=mywar.war The builder would rely on an API that other project could use (Arquilian?).
Ah so more of a command line tool. I can kind of see both use cases TBH. The simplest being a new maven project with a WAR dependency.
Ideally, it would be through a maven plugin, so I could add it to the build. But it would be applied at a later phase, after the WAR was built.
On 9/4/21 1:24 am, James R. Perkins wrote:
Ah so more of a command line tool. I can kind of see both use cases TBH. The simplest being a new maven project with a WAR dependency.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wildfly-extras/wildfly-jar-maven-plugin/issues/227#issuecomment-815940662, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADAZ2FCOWVUCI5D2CVOEIC3THXGTJANCNFSM42SQTBMA.
@chris-corless , the ability to reference an external deployment has been added. We plan to release an early access of the feature in 6.0.0.Alpha1. Let us know if that answers your needs.
@chris-corless , in the end we didn't release a support for "server mode" that was offering the ability to package a war in the bootable JAR.