Thanks for the tip!
I see the benefit just during development. Or is it some other?
Usually when I do changes in Keycloak sources in some module (eg. in
keycloak-model-jpa module) I need to:
1) Build the module with "mvn clean install"
2) Copy the keycloak-model-jpa.jar to the modules in my Wildfly server.
Or rebuild whole distro.
3) Restart the Wildfly
With this, you don't need step 2.
Still embedded undertow is best as you don't even need step 1 when
running KeycloakServer from Idea ;) And for UI only changes, even server
restart is not needed with embedded undertow and -Dresources option.
Marek
On 21/08/17 06:56, Stian Thorgersen wrote:
I knew, but are there any benefits?
On 18 August 2017 at 20:51, Bill Burke <bburke(a)redhat.com> wrote:
> Did you know with a flip of a switch that a jarless Keycloak distro can
> be created? Just edit <root>/distribution/server-provisioning.xml and
> remove extraction params:
>
> <server-provisioning xmlns="urn:wildfly:server-provisioning:1.2"
> extract-schemas="true">
> <feature-packs>
> <feature-pack groupId="org.keycloak"
> artifactId="keycloak-server-feature-pack"
version="${project.version}"/>
> </feature-packs>
> </server-provisioning>
>
> All the module.xml reference maven artifacts and when you boot the
> distro it tries by default to resolve them in ~/.m2, you can even point
> it to a remote distro and it will download the jars.
>
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev