Failed to build parent project for org.apache.logging.log4j:log4j-api:jar:2.25.1

[rob975]

Description

Last week I opened issue #3813 and tested the release candidate for version 2.25.1 as suggested. It worked fine.
Today I upgraded to version 2.25.1 and the issue is not solved.

Configuration

Version: 2.25.1

Operating system: Fedora Linux 42

JDK: Fedora Project OpenJDK 21

Logs

[DEBUG] Error retrieving POM of module-dependency: org.apache.logging.log4j:log4j-api:jar:2.25.1; Reason: Some problems were encountered while processing the POMs:
[WARNING] 'build.plugins.plugin.version' for org.codehaus.gmavenplus:gmavenplus-plugin is missing. @
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @
[WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:build-helper-maven-plugin is missing. @ line 69, column 15
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-enforcer-plugin is missing. @
[ERROR] 'dependencies.dependency.version' for com.google.errorprone:error_prone_annotations:jar must be a valid version but is '${error-prone.version}'. @

Reproduction

As per issue #3813

[ppkarwasz]

Hi @rob975,

It turns out the fix for the error_prone issue was ineffective due to an oversight on my part (see #3822).
The core problem is that we don’t currently have a dedicated test for this scenario—the closest we have is a log event with ERROR severity in the Gradle build (apache/logging-log4j-samples#351).

Does your build actually fail because of this, or is it just logging an ERROR-level message?

I believe this kind of inconsistency between the flattened parent POM and its children will eventually be resolved once we have the opportunity to migrate to Maven 4 (#3780), which handles POM flattening in a more consistent and controlled way.

[ppkarwasz]

Hi @rob975,

Thanks for the PR apache/logging-log4j-samples#352. From that example it looks like the problem causes ERROR and WARN messages, but does not fail the build. Does it fail the build in your original project?

I am classifying this problem as normal priority and we'll fix it in the next release (2.26.0 probably).

I am closing this as duplicate of #3822.