Maven插件获取本地仓库路径失败：调用getLocalRepository()返回null

以下是针对你遇到的问题的几种可行解决思路：

1. 确保插件在正确的构建阶段执行 #

Maven的本地仓库会话在构建早期阶段（如validate、initialize）可能尚未完全初始化，导致getLocalRepository()返回null。你需要将插件绑定到较晚的构建阶段，比如process-resources或之后的阶段。

修改项目pom.xml中的插件配置，指定执行阶段：

<plugin>
  <groupId>com.evalia.tools</groupId>
  <artifactId>tools-maven-plugin</artifactId>
  <executions>
    <execution>
      <phase>process-resources</phase>
      <goals>
        <goal>your-goal-name</goal>
      </goals>
    </execution>
  </executions>
</plugin>

2. 直接注入LocalRepositoryManager #

不要通过MavenSession间接获取本地仓库，而是直接使用@Parameter注入LocalRepositoryManager，这是更可靠的方式：

修改你的抽象基类代码，添加注入：

import org.eclipse.aether.repository.LocalRepositoryManager;
import org.apache.maven.plugins.annotations.Parameter;

public abstract class AbstractDependencyLoaderMojo extends AbstractMojo {
    
    // 原有的session注入保留
    @Parameter(defaultValue = "${session}", property = "session", required = true, readonly = true)
    private MavenSession session;

    // 新增LocalRepositoryManager注入
    @Parameter(defaultValue = "${localRepository}", required = true, readonly = true)
    private LocalRepositoryManager localRepoManager;

    // ... 其他代码

    public void execute() throws MojoFailureException, MojoExecutionException {
        MavenProject project = session.getTopLevelProject();
        // 获取本地仓库路径
        String localRepoPath = localRepoManager.getRepository().getBasedir().getAbsolutePath();
        try {
            injectDependencies(project, localRepoPath);
            postExecute(project);
        } catch (Exception e) {
            throw new MojoFailureException("Something went wrong", e);
        }
    }

    // ... 其他代码
}

3. 使用ArtifactResolver自动解析依赖路径 #

手动拼接依赖路径容易出错（比如快照版本、带分类器的依赖），推荐使用Maven的ArtifactResolver来自动获取依赖在本地仓库的实际路径：

步骤1：注入必要的组件和会话 #

import org.apache.maven.artifact.Artifact;
import org.apache.maven.artifact.DefaultArtifact;
import org.apache.maven.artifact.resolver.ArtifactResolver;
import org.apache.maven.plugins.annotations.Component;
import org.apache.maven.plugins.annotations.Parameter;

public abstract class AbstractDependencyLoaderMojo extends AbstractMojo {
    
    @Parameter(defaultValue = "${project}", required = true, readonly = true)
    private MavenProject project;

    @Component
    private ArtifactResolver artifactResolver;

    @Parameter(defaultValue = "${repositorySystemSession}", required = true, readonly = true)
    private RepositorySystemSession repoSession;

    // ... 其他代码
}

步骤2：修改injectDependencies方法 #

private void injectDependencies(MavenProject project) throws MojoFailureException, MojoExecutionException {
    List<Dependency> dependencies = project.getDependencies();

    GroupIdFilter groupIdFilter = new GroupIdFilter(groupIds);
    ArtifactIdFilter artifactIdFilter = new ArtifactIdFilter(artifactIds);

    if(groupIdFilter.isPresent()){
        dependencies.removeIf(groupIdFilter);
    }

    if(artifactIdFilter.isPresent()){
        dependencies.removeIf(artifactIdFilter);
    }

    List<URL> urls = new ArrayList<>();
    for(Dependency dependency: dependencies){
        // 将Dependency转换为Artifact
        Artifact artifact = new DefaultArtifact(
            dependency.getGroupId(),
            dependency.getArtifactId(),
            dependency.getVersion(),
            dependency.getScope(),
            dependency.getType(),
            dependency.getClassifier(),
            null
        );
        try {
            // 解析Artifact到本地仓库
            artifactResolver.resolve(artifact, project.getRemoteArtifactRepositories(), repoSession);
            // 获取实际文件路径并转为URL
            urls.add(artifact.getFile().toURI().toURL());
        } catch (Exception e) {
            throw new MojoExecutionException("Failed to resolve dependency: " + dependency, e);
        }
    }

    updateClasspath(urls.toArray(new URL[urls.size()]));
}

4. 检查Maven API依赖版本 #

确保你的插件项目中依赖的maven-core、maven-plugin-api等库的版本与你运行的Maven版本兼容。比如，如果使用Maven 3.8.x，插件依赖的maven-api版本建议对齐到3.8.x系列。

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