如何在依赖冲突上失败 Maven 构建

Question

我正在开发一个大型多模块项目，该项目使用内部框架作为其依赖项之一。框架版本在项目开始时在顶级 pom 中设置，并且必须保持不变。如果任何子模块使用不同的版本，我希望构建失败。

我尝试将依赖项声明为单个版本：

<dependency>
  <groupId>framework_snt</groupId>
  <artifactId>SFP</artifactId>
  <version>[6.1]</version>
  <type>pom</type>
</dependency>

我尝试过使用具有禁止依赖项的强制插件：

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-enforcer-plugin</artifactId>
  <version>1.0.1</version>
  <executions>
    <execution>
      <id>enforce-versions</id>
      <goals>
        <goal>enforce</goal>
      </goals>
      <configuration>
        <rules>
          <requireJavaVersion>
            <version>[1.6.0-21]</version>
          </requireJavaVersion>
          <requireMavenVersion>
            <version>[3.0.3]</version>
          </requireMavenVersion>
          <bannedDependencies>
            <excludes>
              <exclude>framework_snt:SFP</exclude>
            </excludes>
            <includes>
              <include>framework_snt:SFP:6.1.2</include>
            </includes>
          </bannedDependencies>
        </rules>
      </configuration>
    </execution>
  </executions>
</plugin>

我也尝试添加<DependencyConvergence/> 标签，如here 所述，但这些方法都不起作用。

所以给定这个顶级 pom 片段：

<project>
  <groupId>glb</groupId>
  <artifactId>GLB</artifactId>
  <packaging>pom</packaging>
  <name>Global</name>
  <version>1.0</version>
  ........
  <dependencies>
    <dependency>
      <groupId>framework_snt</groupId>
      <artifactId>SFP</artifactId>
      <version>[6.1.2]</version>
      <type>pom</type>
    </dependency>
  </dependencies>  
  .....
</project>

还有这个（无效的）子模块：

<project>
  <groupId>glb</groupId>
  <artifactId>CORE</artifactId>
  <packaging>jar</packaging>
  <name>Core</name>
  <version>1.0</version>

  <parent>
    <groupId>glb</groupId>
    <artifactId>GLB</artifactId>
    <version>1.0</version>
  </parent>

  <dependencies>
    <dependency>
      <groupId>framework_snt</groupId>
      <artifactId>SFP</artifactId>
      <version>6.3</version>
      <type>pom</type>
    </dependency>
  </dependencies>
</project>

如何设置 maven，以便在使用上面的子模块时构建会失败，但是当我删除标签 <version>6.3</version> 时它会成功（或者我更改版本以匹配顶级 pom 中的版本？

Answer 1

经过大量搜索和尝试使用各种插件的东西却一无所获，我决定编写自己的插件来进行冲突检查。使用依赖项：树插件源作为基础，我编写了以下内容：

   /**
    * Walks the dependency tree looking for anything marked as a conflict, and fails the build if one is found
    * code ripped from the dependency:tree plugin
    *
    * @param rootNode
    * the dependency tree root node to check
    *
    */
   private void checkForConflicts( DependencyNode rootNode ) throws MojoExecutionException
   {
   StringWriter writer = new StringWriter();
   boolean conflicts=false;

   // build the tree
   DependencyNodeVisitor visitor = new SerializingDependencyNodeVisitor( writer, SerializingDependencyNodeVisitor.STANDARD_TOKENS);
   visitor = new BuildingDependencyNodeVisitor( visitor );
   rootNode.accept( visitor );

   getLog().debug("Root: "+rootNode.toNodeString() );

   DependencyNode node;
   Artifact actual, conflict;
   DependencyTreeInverseIterator iter = new DependencyTreeInverseIterator(rootNode);
   while (iter.hasNext() )
     {
      node = (DependencyNode)iter.next();
      if (node.getState() == DependencyNode.OMITTED_FOR_CONFLICT)
        {
         actual = node.getArtifact();
         conflict = node.getRelatedArtifact();
         getLog().debug("conflict node: " + node.toNodeString() );
         getLog().debug("conflict with: "+conflict.toString() );

         getLog().error(actual.getGroupId()+":"+actual.getArtifactId()+":"+actual.getType()+" Conflicting versions: "+actual.getVersion()+" and "+conflict.getVersion() );
         conflicts=true;
        }
     }

    if (conflicts)
      throw new MojoExecutionException( "version conflict detected");
   }

您可以使用以下方法从现有插件中调用它：

try
  {
   rootNode = dependencyTreeBuilder.buildDependencyTree( project, localRepository, artifactFactory, artifactMetadataSource, null, artifactCollector );
   checkForConflicts( rootNode );
  }
catch ( DependencyTreeBuilderException e)
  {
   throw new MojoExecutionException( "Cannot build project dependency tree", e);
  }

然后在你的插件 pom.xml 中，包含来自现有依赖插件源的依赖项和你的好去处。

这适用于我们的项目 -- 但如果有人知道更清洁或更好的方法，请告诉我。