-
Bug
-
Resolution: Done
-
Critical
-
7.4.4.CR1
-
None
7.4.4.GA-CR1 acceptance test maven-repository-check-valid-POM-and-Metadata-files fails on a pom validation error due to the wrong attribute 'combine.self':
jboss-eap-7.4.4.GA-maven-repository/maven-repository/org/apache/logging/log4j/log4j-core/2.17.1.redhat-00001/log4j-core-2.17.1.redhat-00001.pom 11:42:50 FAIL - productized POM file is not valid, is xmlns="http://maven.apache.org/POM/4.0.0" defined in root element??? 11:42:50 jboss-eap-7.4.4.GA-maven-repository/maven-repository/org/apache/logging/log4j/log4j-core/2.17.1.redhat-00001/log4j-core-2.17.1.redhat-00001.pom:458: element configuration: Schemas validity error : Element '{http://maven.apache.org/POM/4.0.0}configuration', attribute 'combine.self': The attribute 'combine.self' is not allowed. jboss-eap-7.4.4.GA-maven-repository/maven-repository/org/apache/logging/log4j/log4j-core/2.17.1.redhat-00001/log4j-core-2.17.1.redhat-00001.pom fails to validate
This occurs for the poms log4j-core-2.17.1.redhat-00001.pom and log4j-api-2.17.1.redhat-00001.pom.
This issue is already fixed in https://code.engineering.redhat.com/gerrit/gitweb?p=apache/logging-log4j2.git;a=shortlog;h=refs/tags/2.17.1.redhat-00002, we just need to make sure is gets into the next CP.
- is incorporated by
-
JBEAP-23351 (7.4.z) Upgrade org.apache.logging.log4j from 2.17.1.redhat-00001 to 2.17.1.redhat-00002
- Closed