Sylwester Lachiewicz created NIFI-16434:
-------------------------------------------
Summary: Replace maven-dependency-tree and maven-compat with the
Maven and Resolver APIs in the NAR Maven Plugin
Key: NIFI-16434
URL: https://issues.apache.org/jira/browse/NIFI-16434
Project: Apache NiFi
Issue Type: Improvement
Components: Tools and Build
Reporter: Sylwester Lachiewicz
The NiFi NAR Maven Plugin uses two parts of the Maven 3 API that are going
away: maven-dependency-tree, which is planned to be retired
(https://github.com/apache/maven-dependency-tree/issues/151), and maven-compat.
It also passes the ${localRepository} parameter, which Maven 4 no longer
supports, and calls the deprecated ArtifactHandlerManager.addHandlers, which
changes the nar handler for the rest of the build.
The plugin can build its dependency graphs, resolve artifacts and build
dependency projects through maven-core and Maven Resolver instead:
* a DependencyGraphBuilder on ProjectDependenciesResolver for the resolved
graph and the verbose graph used by duplicate-nar-dependencies
* Resolver's RepositorySystem for artifacts and version ranges, in place of
maven-compat's ArtifactResolver
* the session's ProjectBuildingRequest in place of the ${localRepository} and
project.remoteArtifactRepositories parameters
* a session copy with a nar artifact type that does not include its
dependencies, for the provided and duplicate goals only, in place of addHandlers
Pull request: https://github.com/apache/nifi-maven/pull/54
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
