Professional Documents
Culture Documents
wildfly /
quickstart
The quickstart pom.xml file contains a Maven profile named bootable-jar which
configures the bootable JAR building:
<profile>
<id>bootable-jar</id>
<build>
<plugins>
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-jar-maven-plugin</artifactId>
<configuration>
<feature-pack-location>wildfly@maven(org.jboss.un
<layers>
<layer>jaxrs-server</layer>
<layer>microprofile-config</layer>
</layers>
<plugin-options>
<jboss-fork-embedded>true</jboss-fork-embedde
</plugin-options>
</configuration>
<executions>
<execution>
<goals>
<goal>package</goal>
</goals>
https://github.com/wildfly/quickstart/blob/main/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc 1/2
2024. 03. 10. 10:13 quickstart/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc at main · wildfly/quickstart
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
Procedure
After the quickstart application is deployed, the bootable JAR includes the
application in the root context. Therefore, any URLs related to the
Note application should not have the /{artifactId} path segment after
HOST:PORT .
../shared-doc/run-integration-tests-with-bootable-jar.adoc
https://github.com/wildfly/quickstart/blob/main/shared-doc/build-and-run-the-quickstart-with-bootable-jar.adoc 2/2