It will work with either maven ( wildfly-maven-plugin) or jboss-cli.
Its written as a Wildfly/JBoss deployer, so you can use standard
deployment options. Again, also, you can embed providers within EARs
and WARs too, really any deployable component. That's what I love about
the Wildfly Deployment architecture.
On 8/10/16 4:45 PM, Dmitry Telegin wrote:
Hi Bill, great job! Hot [re]deployment of providers was much
anticipated.
Do you think it could be integrated with Maven and/or jboss-cli? For
those extension developers who need to redeploy their providers dozens
of times a day that would be priceless.
Dmitry
> Ok,
>
> New provider deployer exists in master. You can package components in
> any type of deployment. i.e. within a EAR or WAR. Hot deploy works as
> well. The deployers/ directory and deployment-scanner subsystem is now
> back in the server. Also added JTA transactions. So, now when a
> KeycloakSession is created a new JTA transaction is associated with the
> KeycloakTransactionManager. If there was an existing JTA transactionn,
> that transaction is suspended and resumed after the keycloak session
> completes. JTA TransactionManager lookup has an SPI now which you can
> enable/disable in keycloaks-server.json. If no transaciton manager
> exists i.e. within the testsuite, JTA is not used at all.
>
> I'll be documenting all this eventually. Still have some work to do on
> the new user federation spi before that though.
>
> Bill
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev