gnodet commented on issue #12302: URL: https://github.com/apache/maven/issues/12302#issuecomment-4740144540
## Update: hadoop-api-shim failure is caused by invalid POM on Maven Central The `hadoop-api-shim` build failure is **not** caused by `TransitiveDependencyManager` — it is caused by an invalid POM published on Maven Central. [`hadoop-project-3.2.0.pom`](https://repo.maven.apache.org/maven2/org/apache/hadoop/hadoop-project/3.2.0/hadoop-project-3.2.0.pom) contains invalid XML at line 1874: `<Xlint:-unchecked/>` — the `-` after the colon is not a valid XML name start character. Maven 4 correctly rejects this: ``` [WARNING] The POM for org.apache.hadoop:hadoop-common:jar:3.2.0 is invalid, transitive dependencies (if any) will not be available: 1 problem was - [FATAL] Non-parseable POM org.apache.hadoop:hadoop-project:3.2.0: Unable to read model: Unexpected character '-' (code 45) (expected a name start character) at [row,col {unknown-source}]: [1874,12] ``` Because the parent POM is unparseable, `hadoop-common`'s transitive dependencies are unavailable, causing compilation failures. **The scope derivation category (hadoop-api-shim, flink-connector-hive) should be retested with valid POMs** to determine if there is a genuine TransitiveDependencyManager regression independent of the invalid POM issue. The enforcer rule category (guacamole-client, logging-log4j-samples, netbeans-html4j) may still be a genuine TransitiveDependencyManager issue — needs further investigation. _Claude Code on behalf of Guillaume Nodet_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
