One module per jar, yes...
Finished all the modules, now setting things up....Sorry, I'm distracted
by deflategate and superbowl this week :)
On 1/22/2015 4:49 PM, Stan Silvert wrote:
On 1/22/2015 4:25 PM, Stan Silvert wrote:
> You could also try using aggregator modules like org.jboss.as.aggregate
> and javaee.api. That way, you retain the flexibility of having each jar
> in its own module but you can still reference the groups.
I just realized that this is probably what you were talking about.
You'll still retain one module per jar?
>
> BTW, I'm back up and running. Woo Hooooo!
>
> On 1/22/2015 3:14 PM, Bill Burke wrote:
>> Hey,
>>
>> I was thinking of having a few aggregate modules instead of having one
>> jboss-deployment-structure.xml that includes everything (50+ modules).
>>
>> keycloak-server - includes base SPIs and keycloak-providers module
>> keycloak-adapter
>> keycloak-providers - includes JPA and infinispan providers by default
>> keycloak-mongo-providers - all stuff that uses mongo
>> keycloak-jpa-providers - all stuff that uses jpa
>> keycloak-infinispan-providers - all stuff that uses infinispan
>> keycloak-social-plugins - all social provider plugins
>>
>> This way, if dependencies need to be added/removed/modified, you don't
>> have to edit the WAR.
>>
>> Sorry I've taken so long... A lot of distractions this week.
>>
>>
> _______________________________________________
> 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
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com