如何定位Maven构建插件中依赖项的JAR文件路径

要定位<plugin>标签中依赖项的本地M2仓库路径，核心是通过Maven的ArtifactResolver组件将插件的Dependency转换为Artifact实例，进而获取本地文件路径。以下是具体实现方案：

1. 注入必要的Maven核心组件 #

在自定义插件类中，通过Maven的依赖注入机制获取所需核心组件：

import org.apache.maven.artifact.Artifact;
import org.apache.maven.artifact.factory.ArtifactFactory;
import org.apache.maven.artifact.resolver.ArtifactResolver;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.maven.plugins.annotations.Component;
import org.apache.maven.plugins.annotations.Parameter;
import org.apache.maven.plugins.annotations.Mojo;
import org.apache.maven.project.MavenProject;
import org.apache.maven.model.Plugin;
import org.apache.maven.model.Dependency;

import java.io.File;
import java.util.List;

@Mojo(name = "find-plugin-deps-path")
public class PluginDependencyPathMojo extends AbstractMojo {

    @Component
    private ArtifactResolver artifactResolver;

    @Component
    private ArtifactFactory artifactFactory;

    @Parameter(defaultValue = "${localRepository}", readonly = true)
    private ArtifactRepository localRepository;

    @Parameter(defaultValue = "${project}", readonly = true)
    private MavenProject project;

    @Override
    public void execute() throws MojoExecutionException {
        // 核心逻辑实现
    }
}

2. 遍历插件并解析依赖路径 #

在execute方法中，遍历项目的插件列表，将每个插件的依赖转换为Artifact并解析本地路径：

@Override
public void execute() throws MojoExecutionException {
    List<Plugin> plugins = project.getBuild().getPlugins();
    for (Plugin plugin : plugins) {
        getLog().info("处理插件: " + plugin.getGroupId() + ":" + plugin.getArtifactId());
        
        List<Dependency> pluginDeps = plugin.getDependencies();
        for (Dependency dep : pluginDeps) {
            try {
                // 创建对应依赖的Artifact实例
                Artifact artifact = artifactFactory.createArtifact(
                        dep.getGroupId(),
                        dep.getArtifactId(),
                        dep.getVersion(),
                        dep.getScope(),
                        dep.getType()
                );

                // 解析Artifact（确保本地仓库存在，缺失时会尝试从远程仓库下载）
                artifactResolver.resolve(artifact, project.getRemoteArtifactRepositories(), localRepository);

                // 获取本地JAR文件路径
                File jarFile = artifact.getFile();
                if (jarFile != null && jarFile.exists()) {
                    getLog().info("依赖 " + dep.getGroupId() + ":" + dep.getArtifactId() + " 的路径: " + jarFile.getAbsolutePath());
                } else {
                    getLog().warn("未找到依赖 " + dep.getGroupId() + ":" + dep.getArtifactId() + " 的本地文件");
                }
            } catch (Exception e) {
                getLog().error("解析依赖 " + dep.getGroupId() + ":" + dep.getArtifactId() + " 失败", e);
            }
        }
    }
}

关键说明 #

• 之前方法无效的原因：项目的依赖树（DependencyTree）仅包含主项目的依赖，插件的依赖属于插件自身的独立类路径，不会被纳入主依赖树，因此需要单独解析。
• ArtifactResolver的作用：验证依赖是否存在于本地仓库，若缺失会自动从配置的远程仓库下载（需 Maven 配置允许）。
• 非JAR依赖处理：如果依赖的type为pom等非JAR类型，getFile()会返回null，需根据需求过滤或另行处理这类情况。

内容的提问来源于stack exchange，提问作者rveach