-
Notifications
You must be signed in to change notification settings - Fork 4
XIVY-16828 Process issues not reported as [WARNING] #700
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
Conversation
note that log4j-over-slf4j1 still works in combination with our log4j2 engine. |
Here's evidence, that the fix works: https://jenkins.ivyteam.io/job/project-build-plugin/job/mavenWarn2/7/maven-warnings/ However, since we have broken that feature a long time ago ... I'll merge it down to all affected LTS versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strange!
So we release a new project-plugin version 13.1.0.1?
I wouldn't break the pattern; up to now just major and minor reflects the compatible release train. |
When did we decide that? |
A decade before we started to do ADR's 😉 |
enables our configuration for
[WARNING]
prefixed brackets, just like maven does, .... while the default of slf4j is[WARN]
.since slf4j 2.x half-way removed that feature, we have to downgrade to 1.7.x: