Try the new deployment approach, check out docs and examples for details,
but in summary you add a jboss-deployment-structore.xml for your
dependencies or you can also include deps inside the deployment itself and
you put it into standalone/deployments.
You can also still use the modules approach in 2.5.1. Providers directory
doesn't allow having any additional dependencies, so that only works for
providers that have no need for additional dependencies.
On 30 January 2017 at 16:35, Giordano, Antonio <A.Giordano(a)klopotek.it>
wrote:
Hi all,
We are moving from keycloak 1.7 to 2.5.1 and we have some troubles in the
deployment of a jar relative to our user storage provider.
In the old version we deploy all jars and properties with jboss modules
logic but in new version there is a specific folder "providers" where we
have to deploy our user storage provider.
Unfortunately seems that our jar can't use resources loaded in modules
section of wildfly (other jars or props) and needs all resources in his
package.
My question is: which is the correct way in 2.5.1 to deploy a keycloak
provider that use resources defined in wildfly classpath via modules logic?
Thanks for your help
agi
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user