You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be cool if TravisCI could be configured for this repository to build the JARs and upload them to the releases section.
I love your work and normally end up copying it over to a new repository, with travis configured to push up a JAR. It makes it easy for docker-compose examples to just fetch the JAR remotely.
The text was updated successfully, but these errors were encountered:
@thomasdarimont Is the silence on this issue because there needs to be some investment on the part of the user? That is, since there is no guarantee (from you or Keycloak) that these plugins perform as advertised, you don't want to make it too easy for these extensions to be used improperly?
From a different perspective, the strict requirement to have mvn available and an already-compiled source of keycloak/keycloak available significantly increases the cost of entry to using any of these (incredible-looking) extensions. I'm opting to try it by using the maven docker image to see if I can get it to work, but if not then I'll be unable to use anything here.
I argue that many users of keycloak who would be candidates for using these extensions are not java programmers. (I'm one of them.)
I appreciate the effort and organization you've put in to these extensions.
It would be cool if TravisCI could be configured for this repository to build the JARs and upload them to the releases section.
I love your work and normally end up copying it over to a new repository, with travis configured to push up a JAR. It makes it easy for docker-compose examples to just fetch the JAR remotely.
The text was updated successfully, but these errors were encountered: