Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Outdated version properties in keycloak-parent pom.xml
See original GitHub issueDescribe the bug
In keycloak-parent pom.xml are still some old/outdated version properties, e.g.
<resteasy.version>3.15.1.Final</resteasy.version> - where as the Keycloak 16.0.0 server runs more recent versions of dependencies, e.g. the RestEasy version is on 4.7.2.Final.
This leads to errors and ClassNotFoundExceptions during runtime when using dependency versions from the parent pom during compile time.
Version
16.0.0
Expected behavior
All version properties in keycloak-parent:pom.xml reflect the actual versions of the dependencies in the running server.
Actual behavior
The keycloak-parent:pom.xml has still some old/outdated dependency version properties.
How to Reproduce?
Look into the parent pom.xml, e.g. https://github.com/keycloak/keycloak/blob/6c12c188542aeacc6d40aff9160e83b6a12f5b97/pom.xml#L96
Anything else?
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Unfortunately, this is bad developer experience. With every version upgrade, developers have to investigate time-consuming all necessary dependency and library updates within the underlying server. Redundant work for a lot of people.
This would be ok, if it would be very easy to use Keycloak in various runtimes. But actually it’s only usable with the provided Wildfly, and in future with Quarkus runtime - which is great and I really appreciate this. But today I would expect that the product gives me all the necessary dependencies which are available, not just saying “hey, it’s the runtime, it’s not our product”. Actually, the runtime is part of the product. Just saying.
keycloak-parent isn’t a BOM and obviously shouldn’t be used as such. We do have the SPI BOM for this purpose, now this issue isn’t valid, but made me realise that the SPI BOM is not valid either, so we can fix this there at least for now.
I’ll close this issue and open another one against the proper BOM tomorrow, and get this fixed in 17.0.0, or 16.0.1 (if we do one, but I’m not doing one just for this issue).