[keycloak-dev] jarless Keycloak distro
bburke at redhat.com
Mon Aug 21 10:02:50 EDT 2017
Helps in dev a lot like you said.
I was told Wildfly team builds it for their arquillian test harness.
Not sure why it would be beneficial.
Could define "profiles" that are small downloads and ready to run.
At least for Wildfly, saves disk space or allows for a mounted NFS
shared maven repo.
Jason Greene was talking about using shared docker data volumes +
mmapped jars. This kind of structure might be able to facilitate that.
On 8/21/17 4:49 AM, Marek Posolda wrote:
> 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
> 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 at 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"
>>> <feature-pack groupId="org.keycloak"
>>> 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 at lists.jboss.org
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
More information about the keycloak-dev