Re: [keycloak-dev] release? Stan?
One slightly related issue. I just did some testing and figured that
eap6.3 and as7 distribution were broken as they excluded
keycloak-subsystem . I've fixed that and EAP 6.3 works fine now. But on
AS 7.1.1 the keycloak-subsystem doesn't work and I have:
Caused by: java.lang.ClassNotFoundException:
org.jboss.as.controller.OperationDefinition from [Module
"org.keycloak.keycloak-subsystem:main"
I am seeing options like:
1) Drop AS7 support
2) Revert AS7 specific subsystem
3) Do some hack in keycloak-subsystem to have it working on AS 7.1.1 (is
it doable?)
Anything else I am missing?
Marek
On 2.12.2014 14:38, Bill Burke wrote:
On 12/2/2014 7:55 AM, Stan Silvert wrote:
> On 12/2/2014 4:52 AM, Stian Thorgersen wrote:
>> Should we upgrade to WF 8.2 and also do some changes to the distro before
release?
> I don't see a reason not to go to WF 8.2. If we do that, let me know so
> I can run a quick smoke test on the subsystem before we release.
>> With regards to distro we should move the adapters and examples into separate
downloads. Also, we should move the examples into a separate github project
(keycloak/keycloak-examples). This will make it easier for those that wants to fork the
examples separately.
>>
>> Also, we should consider a download based on the web-lite profile. For non-JavaEE
apps, containers (Docker) and those that want to run a standalone KC server it would be
nice to have a small as possible distro.
> Depending on how the feature pack turns out, we might be able to offer
> many flavors of the appliance distro without any additional effort. We
> could have:
> EAP6 + Keycloak
> AS7 + Keycloak
> WF8 (web) + Keycloak
> WF8 (full) + Keycloak
> WF 9 beta (web) + Keycloak
> WF 9 beta (full) + Keycloak
> etc.
>
IMO, we just need:
* war-dist
* appliance-dist
Appliance distribution would have the most stable platform available.
Since we can't distribute EAP, then it would be the most stable and
maintained version of Wildfly that allows us to cluster and deploy Keycloak.