slachiewicz opened a new pull request, #566: URL: https://github.com/apache/felix-dev/pull/566
maven-dependency-tree is planned to be retired (apache/maven-dependency-tree#151). maven-bundle-plugin uses only its `DependencyGraphBuilder`, which in 3.3.0 is a thin layer over maven-core: `ProjectDependenciesResolver.resolve()` with a resolution filter that downloads no artifact files, then a conversion of each Resolver node into its own node type. This calls `ProjectDependenciesResolver` the same way and works on the Resolver `DependencyNode` directly: - `BundlePlugin.collectDependencyGraph(MavenProject)` builds the graph; `toArtifact(node, project)` turns a node into a Maven `Artifact` with the scope and optional flag of its dependency, or the project artifact for the root, as maven-dependency-tree did. - `updateExcludesInDeps` (dependency-reduced POM) reads group and artifact ids from the Resolver nodes; the logic is unchanged. - `BundleAllPlugin.bundleAll` walks the same graph and converts each node with `toArtifact`. - The `maven-dependency-tree` dependency is removed; `ProjectDependenciesResolver`, `RepositoryUtils` and the Resolver API come from the `provided` maven-core. Verified: - `mvn verify`: 26 unit tests and all 12 invoker ITs pass, including `dep-reduced`. - On the `dep-reduced` IT project, the dependency-reduced POM is identical to what the released 6.2.0 writes (apart from the plugin version in it), and `bundle:bundleall -DmaxDepth=2` bundles the same artifacts with the same log output as 6.2.0. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
