Yul checks prospective pom.xml edits and needs to inspect every directly declared coordinate whose version can change. The Maven parser currently returns effective project dependencies from ep.Dependencies, which omits several declarations that Yul checks today:
- parent
dependencyManagement- build plugins
- plugin dependencies
pluginManagement- build extensions
- each of those declarations inside profiles
Could the Maven parser expose these version-bearing references while preserving enough information to distinguish their kind and profile? Consumers comparing before and after manifest content need the declarations themselves rather than only the effective dependency set.
This affects manifests v0.6.1. A characterization suite for the intended consumer behavior is in chains-project/yul#1.
Yul checks prospective
pom.xmledits and needs to inspect every directly declared coordinate whose version can change. The Maven parser currently returns effective project dependencies fromep.Dependencies, which omits several declarations that Yul checks today:dependencyManagementpluginManagementCould the Maven parser expose these version-bearing references while preserving enough information to distinguish their kind and profile? Consumers comparing before and after manifest content need the declarations themselves rather than only the effective dependency set.
This affects
manifestsv0.6.1. A characterization suite for the intended consumer behavior is in chains-project/yul#1.