Generally Speaking

For the most part, WildFly Swarm is consumed through Maven artifacts, resembling pom.xml entries such as

<dependency>
  <groupId>org.wildfly.swarm</groupId>
  <artifactId>jaxrs</artifactId>
</dependency>

We highly recommend using one of our BOMs so that you don’t need to specify versions of each component you bring in:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.wildfly.swarm</groupId>
      <artifactId>bom<artifactId>
      <version>${version.wildfly-swarm}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

For more information, please see How to use a BOM in the documentation.

Directly Downloadable

We do provide a few directly downloadable and usable items:

SwarmTool

SwarmTool can be used to take an existing .war and "swarmify" it.

MicroProfile Server

Our MicroProfile server can be used to run an existing MicroProfile-compliant .war file.

MicroProfile + JPA Server

Our MicroProfile with JPA server can be used to run MicroProfile microservices that require JPA that are present in a war file.

Web Server

Similar to the MicroProfile server, Web provides a Hollow jar that’s equivalent to the Web Profile from Java EE.

Keycloak Server

Our Keycloak standalone server may be used to run your own Keycloak easily.

Management Console Server

Our runnable WildFly Management Console may be used to manage your WildFly Swarm application (if they include the management fraction).

Swagger UI

Our runnable Swagger UI server makes it easy to launch the Swagger UI.