gnodet commented on issue #12302:
URL: https://github.com/apache/maven/issues/12302#issuecomment-4742750708
## Update: Category 1 (scope derivation) was a false positive
After comparing `toolbox:tree -DverboseTree` output between Maven 3 and
Maven 4 for `flink-connector-hive`, the remaining Category 1 project also turns
out to be caused by invalid Hadoop POMs, not by scope derivation changes.
**`flink-connector-hive`** depends on `hadoop-mapreduce-client-core:3.1.0`
(provided) and `hadoop-yarn-registry:3.1.0` (compile). Both transitively depend
on `hadoop-project:3.1.0`, which — like `hadoop-project:3.2.0` — contains
invalid XML (`<Xlint:-unchecked/>`).
**Maven 3 verbose tree** shows all Hadoop transitives resolved:
```
+- hadoop-yarn-registry:3.1.0 [compile]
| +- hadoop-auth:3.1.0 [compile]
| +- hadoop-annotations:3.1.0 [compile]
| +- hadoop-yarn-api:3.1.0 [compile]
| +- hadoop-common:3.1.0 [compile]
+- hadoop-mapreduce-client-core:3.1.0 [provided]
| +- hadoop-yarn-client:3.1.0 [provided]
| +- hadoop-annotations:3.1.0 [compile]
```
**Maven 4 verbose tree** shows both Hadoop subtrees stripped:
```
WARNING: The POM for hadoop-mapreduce-client-core:3.1.0 is invalid,
transitive dependencies (if any) will not be available
WARNING: The POM for hadoop-yarn-registry:3.1.0 is invalid,
transitive dependencies (if any) will not be available
+- hadoop-yarn-registry:3.1.0 [compile] ← no children
+- hadoop-mapreduce-client-core:3.1.0 [provided] ← no children
```
Both `hadoop-api-shim` (hadoop-project:3.2.0) and `flink-connector-hive`
(hadoop-project:3.1.0) fail for the same reason: Maven 4 correctly rejects
invalid XML in the parent POM while Maven 3 silently accepts it.
**This issue now only covers Category 2** (managed version application to
transitive dependencies). The issue body has been updated accordingly.
--
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]
