-1000. But you've already done this with the quickstarts against my
wishes. You know why, but I'll rehash anyways:
* Examples will get out of sync
* Examples will end up not working
* Examples need to be tied to a specific release as APIs and SPIs change
* Users won't know they exist
* Examples won't pick up IDE refactorings of our SPIs and APIs because
people will forget to include them.
There's really no good reason to have quickstarts and examples in a
separate repo and a separate build other than "Wildlfy does it."
On 6/29/17 5:44 AM, Bruno Oliveira wrote:
+1 that would be great
On 2017-06-28, Stian Thorgersen wrote:
> At times there are extensions and examples that we don't want to include in
> the main repository. This could be for several reasons, including:
> * We don't have the resources to maintain and support it
> * We don't believe it's generic enough
> * Examples that are to complex
> However, these can still be useful for some people. So I'm thinking about
> how we can provide community maintained extensions and examples.
> A very simple idea would be to add a page on our website that links to the
> relevant repository and documentation. To contribute you would setup your
> own Github repository, documentation and also a download if you want. Then
> you'd send a PR to the website to add your extension or example.
> keycloak-dev mailing list
keycloak-dev mailing list