4.2.4: Use BOMs to manage versions of junit and langchain4j #10363
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
barchetta
added
build
dependencies
oracle-contributor-agreement
bot
added
the
OCA Verified
danielkec
previously approved these changes
Jul 10, 2025
|
The issues with the spring eureka integration tests is caused by the broken langchain4j bom's that are managing versions of things like junit and logback. Langchain4j is fixing their bom's but for 0.36.2 they are broken. So I'm going to bail on this PR - and we'll address this in 4.3.0 when we pick up later versions of langchain4j with fixed boms. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use BOMs to manage versions of junit and langchain4j
This does not upgrade langchain4j
This upgrades junit to 5.11.3 to align with the version of junit-platform-testkit