当资源过滤无法找到属性时，Maven会警告或失败目标(Maven warn or fail goal when resource filtering cannot find a property)

 我开始研究一个记录不完整的Maven项目。 我已经为项目设置了我的配置文件，但我可能会或可能不会缺少资源过滤期间使用的属性定义。 默认情况下，如果未在筛选文件中定义属性，则变量名称将保留在复制的资源中，Maven将以静默方式继续。 
 
 在这种情况下，有没有办法迫使Maven快速失败？ 
 
 作为一个最小的例子，拿这个pom， 
 
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.mycompany.app</groupId>
  <artifactId>my-app</artifactId>
  <packaging>jar</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>my-app</name>
 <build>
  <resources>
   <resource>
    <directory>src/main/resources</directory>
    <filtering>true</filtering>
   </resource>
  </resources>
 </build>
 <profiles>
  <profile>
   <id>production</id>
   <properties>
    <foo>Craig</foo>
   </properties>
  </profile>
 </profiles>
</project>
 
 并有一个资源来过滤： 
 
 echo 'Hello, my name is ${foo}!' > src/main/resources/test
 
 然后运行mvn clean install -Pproduction生成一个文件，上面写着Hello, my name is Craig! 运行mvn clean install会生成一个说Hello, my name is ${foo}!的文件Hello, my name is ${foo}! 。 
 
 所以我的问题是; 在第二种情况下如何强制Maven失败？ 

I am starting to work on a poorly documented Maven project. I have set up my profile for the project but I may or may not be missing property definitions that used during resource filtering. By default, if a property is not defined in a filtered file, the variable name is left in the copied resource and Maven continues silently.
 
Is there a way to force Maven to fast-fail in this case?
 
As a minimal example, take this pom,
 
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.mycompany.app</groupId>
  <artifactId>my-app</artifactId>
  <packaging>jar</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>my-app</name>
 <build>
  <resources>
   <resource>
    <directory>src/main/resources</directory>
    <filtering>true</filtering>
   </resource>
  </resources>
 </build>
 <profiles>
  <profile>
   <id>production</id>
   <properties>
    <foo>Craig</foo>
   </properties>
  </profile>
 </profiles>
</project>
 
And have a resource to filter:
 
 echo 'Hello, my name is ${foo}!' > src/main/resources/test
 
Then running mvn clean install -Pproduction produces a file that says Hello, my name is Craig! while running mvn clean install produces a file that says Hello, my name is ${foo}!. 
 
So my question is; how do I force Maven to fail in the second case?

原文：https://stackoverflow.com/questions/17732618