Skip to content

Fix log4j bad versions#389

Open
mgaffigan wants to merge 3 commits into
OpenIntegrationEngine:mainfrom
mgaffigan:fix/junit-bad-versions
Open

Fix log4j bad versions#389
mgaffigan wants to merge 3 commits into
OpenIntegrationEngine:mainfrom
mgaffigan:fix/junit-bad-versions

Conversation

@mgaffigan

Copy link
Copy Markdown
Contributor

main (ac47cc8) has a bad combination of log4j libs which prevents the server from booting. They were not caught on #370 since #294 has not yet merged to start the server as part of CI, so approvers got happy green checkmarks when everything is broken.

  • Updates log4j to matching versions
  • Fixes secondary log4j discovery issue
  • Updates log4j to current latest

Tested and passed with #294 and through manual tests.

Signed-off-by: Mitch Gaffigan <mitch.gaffigan@comcast.net>
Signed-off-by: Mitch Gaffigan <mitch.gaffigan@comcast.net>
Signed-off-by: Mitch Gaffigan <mitch.gaffigan@comcast.net>
@github-actions

Copy link
Copy Markdown

Test Results

655 tests  +1   655 ✅ +1   3m 26s ⏱️ +44s
109 suites +1     0 💤 ±0 
109 files   +1     0 ❌ ±0 

Results for commit c173fac. ± Comparison against base commit ac47cc8.

@mgaffigan mgaffigan changed the title Fix junit bad versions Fix log4j bad versions Jul 25, 2026
<sha256 value="ba6d68eeab3a1cc13a77a8ade2197ff9a32aa1cffeac72847d49badd82e1b9ce" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson" name="jackson-bom" version="2.19.2">

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what's going on with the jackson stuff. I don't think it is supposed to be in this PR? Additionally, this version doesn't match what is in libs.versions.toml, and there are already newer versions specified in this file.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was generated by the normal Gradle regen command. I assumed it had some interaction with another package or was missed in a prior PR.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tonygermano, is this blocking or are we good to merge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants