WildFly Swarm provides a mechanism for building applications as uber jars, with just enough of the WildFly application server wrapped around it to support each application's use-case.
Note: WildFly Swarm requires Maven 3.1.x or higher for building your application.
In a normal WAR-based maven pom.xml
, simply add the following
<plugin>
<groupId>org.wildfly.swarm</groupId>
<artifactId>wildfly-swarm-plugin</artifactId>
<version>${version.wildfly-swarm}</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>package</goal>
</goals>
</execution>
</executions>
</plugin>
This will take the .war
file normally created by your build, and wrap
it in the wildfly-swarm mechanisms.
If you normally produce myapp-1.0.war
, in your target/
directory will
then also be present a myapp-1.0-swarm.jar
.
In order to specify the portions of the WildFly AS your application needs,
your pom.xml
should specify some of the following dependencies within
the org.wildfly.swarm
Maven group-id:
- bean-validation
- ee
- io
- jaxrs
- logging
- naming
- request-controller
- security
- transactions
- undertow
- weld
- and many more!
Issue are being tracked using the JBoss issue tracking system (JIRA). Bug reports and feature requests are greatly appreciated.
For a more complete set of documentation, go to the WildFly Swarm User's Guide.
- We hang out in
#wildfly-swarm
on irc.freenode.net. - Logs can be found here