Skip to content
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

Upgrade to newer log4j 1.2.x for munged library? #17

Open
apjanke opened this issue Sep 10, 2022 · 0 comments
Open

Upgrade to newer log4j 1.2.x for munged library? #17

apjanke opened this issue Sep 10, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@apjanke
Copy link
Member

apjanke commented Sep 10, 2022

Since our munged log4j 1.2.x won't be addressed by any other software, maybe no reason to stick on exactly 1.2.15. Maybe upgrade to a newer version in the 1.2.x series? Check their release notes and see if that's a good idea.

Log4Shell did not affect any 1.2.x; only 2.x, so that's not a concern here.

The log4j 1.2 series only has two more versions: 1.2.16 and 1.2.17. They're both bugfix releases. I don't see anything major, but might want to pick them up anyway by getting 1.2.17.

Loooot of bugfixes in 1.2.16. 1.2.16 makes those Sun Java jmx and jms JARs optional in the build. Might be convenient.

Make javamail, jmx, jms dependencies optional in pom.xml. Fixes 43304

Also "reasonable thread names".

Part of janklab/slf4m-jankalog#4.

@apjanke apjanke added the enhancement New feature or request label Sep 10, 2022
@apjanke apjanke self-assigned this Sep 10, 2022
@apjanke apjanke added this to the 1.4.0 milestone Sep 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant