Skip to content

fix: Define version of error_prone_annotations in parent POM #3785

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 1 commit into from
Jun 28, 2025

Conversation

ppkarwasz
Copy link
Contributor

This change explicitly defines the version of the error_prone_annotations dependency in the log4j parent POM.

Previously, the version was inherited via the error-prone.version property from logging-parent. However, because the log4j-bom POM is flattened during publication, this property no longer resolves in consumer projects.

Fixes #3779

This change explicitly defines the version of the `error_prone_annotations` dependency in the `log4j` parent POM.

Previously, the version was inherited via the `error-prone.version` property from `logging-parent`. However, because the `log4j-bom` POM is flattened during publication, this property no longer resolves in consumer projects.

Fixes #3779
@ppkarwasz ppkarwasz merged commit e08c7ba into 2.x Jun 28, 2025
11 checks passed
@ppkarwasz ppkarwasz deleted the fix/3779_error-prone branch June 28, 2025 07:11
@github-project-automation github-project-automation bot moved this from To triage to Done in Log4j bug tracker Jun 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Missing property in the log4j-parent pom file in version 2.25.0
2 participants