2014-06-12 8 views
16

Ho il seguente pom.xml. Quando eseguo mvn clean resources:testResources, le mie risorse di test non vengono filtrate. Perché?Come si filtrano le risorse di test in Maven?

<?xml version="1.0" encoding="UTF-8"?> 
<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.example</groupId> 
    <artifactId>foo</artifactId> 
    <version>0.0.1</version> 
    <packaging>jar</packaging> 
    <name>foo</name> 

    <dependencies> 
     <dependency> 
      <groupId>junit</groupId> 
      <artifactId>junit</artifactId> 
      <version>4.11</version> 
      <scope>test</scope> 
     </dependency> 
    </dependencies> 

    <build> 
     <resources> 
      <resource> 
       <directory>src/test/resources</directory> 
       <filtering>true</filtering> 
      </resource> 
     </resources> 
    </build> 
</project> 

risposta

37

I resources e resource elementi sono per la resources:resources obiettivo. resources:testResources utilizza gli elementi testResources e testResource.

la correttezza pom.xml è:

<?xml version="1.0" encoding="UTF-8"?> 
<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.example</groupId> 
    <artifactId>foo</artifactId> 
    <version>0.0.1</version> 
    <packaging>jar</packaging> 
    <name>foo</name> 

    <dependencies> 
     <dependency> 
      <groupId>junit</groupId> 
      <artifactId>junit</artifactId> 
      <version>4.11</version> 
      <scope>test</scope> 
     </dependency> 
    </dependencies> 

    <build> 
     <testResources> 
      <testResource> 
       <directory>src/test/resources</directory> 
       <filtering>true</filtering> 
      </testResource> 
     </testResources> 
    </build> 
</project> 
+1

Ancora un altro Maven sottigliezza ... – Stephan

+3

@Stephan sembra proprio una buona idea per separare le risorse e le risorse di prova no? –

+0

@ MichaelLaffargue Hai ragione. Tuttavia, il modo in cui l'OP ha cercato nella sua domanda è più ovvio. – Stephan

Problemi correlati