Repository navigation
Replies: 3 comments 2 replies
|
I'd propose that: Would not include the testsuite at all, then you could choose to run everything with: Or, just run the testsuite with: Further, when the testsuite is enabled from the root, the distribution should also be built, and we need to make sure there are dependencides on distribution bits within testsuite so a Maven reactor build works properly. For example the following should work: Or, if I want to rebuild the server dist, then run testsuite I could do: |
|
Basically using |
|
I really like this idea! Today, I just fork Keycloak repo and run |
|
It's solved! |
|
This is great news. Until version 16.1.0, everything is working well with run/debug/ run tests from Intellij with rare errors. As @stianst said attention must be in Keycloak X ( quarkus). Moreover, I believe that you should try to migrate all main Keycloak modules to Java 11. It is problematic using version Java 7 (!) in some modules and use simultaneously Quarkus which is running in Java 11 at least. This make also problems in IDE. I could try make a PR for this if Keycloak team will be intrested. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
At the moment it's a bit of a PITA to build Keycloak, especially following the instructions in https://github.com/keycloak/keycloak/blob/main/docs/building.md.
I'm also having constant issues with InteliJ and weird build errors there. Not sure if that's a common thing, but seems all the
magicstuff around the new store, javascript adapters, npm modules, etc. are all a bit of a PITA?Some issues with it:
mvn clean installbuilds and runs the testsuite, which takes an enormous amount of timeThere's also some issues with missing dependencies especially around the testsuite not having dependencies on the distribution.
A couple things here that will help:
defaultbuildAll reactions