keycloak-scim/distribution/feature-pack-builds
2015-05-05 20:40:05 +02:00
..
adapter-only KEYCLOAK-1183 Split subsystem into separate server and adapter subsystems 2015-05-05 20:40:05 +02:00
server-and-adapter Rename feature pack artifacts. Fix empty content directory. 2015-05-05 20:40:04 +02:00
server-only Rename feature pack artifacts. Fix empty content directory. 2015-05-05 20:40:04 +02:00
pom.xml Create builds based on WildFly 9 feature packs. 2015-05-05 20:40:04 +02:00
README.md Update README.md 2015-05-05 20:40:04 +02:00

Keycloak Feature Pack Builds

The feature pack builds rely on WildFly Feature packs to create different combinations of Keycloak server/adapter and WildFly web/full.

Types of Builds Created

The three directories under feature-pack-builds are adapter-only, server-only, and server-and-adapter.

  • adapter-only - A WildFly server with the Keycloak adapter subsystem added. This build is based on the WildFly Web Feature Pack. keycloak-adapter-feature-pack contains all the modules needed to run the Keycloak WildFly Adapter. Therefore, the build is org.wildfly:wildfly-web-feature-pack + org.keycloak:keycloak-adapter-feature-pack.
  • server-only - A WildFly server with the Keycloak adapter subsystem added. This build is based on the WildFly Full Feature Pack. keycloak-server-feature-pack contains all the modules needed to run the Keycloak Server without those already provided by the full WildFly Server. Therefore, the build is org.wildfly:wildfly-feature-pack + org.keycloak:keycloak-server-feature-pack.
  • server-and-adapter is the same thing as server-only except it also includes keycloak-adapter-feature-pack. Therefore, the build is org.wildfly:wildfly-feature-pack + org.keycloak:keycloak-server-feature-pack + org.keycloak:keycloak-adapter-feature-pack.

Building

Each of the three types of builds in turn creates a build version and a dist version.

The build version is a server that uses the new WildFly 9 feature whereby maven artifacts are not bundled with the server. Instead, they are looked up in a repository.

For the dist version, these artifacts are copied into the server itself and no maven repo is required.

By default, the dist version does not get built. To build it, specify the jboss-release profile:

mvn install -Pjboss-release