Skip to content

INT-4376: Upgage to Log4J 2 #2321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 11, 2018
Merged

Conversation

artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-4376

  • Deprecate Log4J 1.x components in favor of newly added
    a Log4j2LevelAdjuster JUnit @Rule
  • Update all the logging configuration to Log4J 2

JIRA: https://jira.spring.io/browse/INT-4376

* Deprecate Log4J 1.x components in favor of newly added
a `Log4j2LevelAdjuster` JUnit `@Rule`
* Update all the logging configuration to Log4J 2
@artembilan
Copy link
Member Author

@wilkinsona ,

tell us, please, what a trick we may add to our Gradle config to ignore compile ('log4j:log4j:1.2.17', optional) dependency during springIoCheck task? Or maybe even whole spring-integration-test-support module?
Or the easiest way to reinstate Log4J 1.x dependency in IO Platform? Than we will stick with it there until our Spring Integration 5.1.

Thank you for any wisdom and advises!

@wilkinsona
Copy link
Member

I've reinstated Log4j 1 dependency management in Cairo. You should see the benefits of that once I've fixed up a few other things and can then get a new snapshot published

@garyrussell garyrussell merged commit 30450c4 into spring-projects:master Jan 11, 2018
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.

3 participants