[MRESOURCES-8] maven-resources-plugin ignores configuration/resources property (add a new mojo to copy resources)

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1, 2.2
• Fix Version/s: 2.3
• Assignee: Olivier Lamy
• Reporter: Leszek Gawron
• Created: 07/Jan/06 17:08
• Updated: 14/Sep/08 05:21
• Resolved: 13/Sep/08 16:38

Description

I am evaluating maven + eclipse combo. In a trivial POM filtered resources exist only in target/classes. If one executes Project -> Clean under eclipse this information is lost. If filtered resources would appear as source folder they would survive cleaning and not got overriden by unfiltered ones.

I have been trying to implement a scenario which would allow filtered resources to appear as "static" source folder under eclipse.
The POM explains it best:

<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.mobilebox.squash.client</groupId>
  <artifactId>squash-client</artifactId>
  <packaging>jar</packaging>
  <version>1.0-SNAPSHOT</version>
  <name>Maven Quick Start Archetype</name>
  <url>http://maven.apache.org</url>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-resources-plugin</artifactId>
        <executions>
          <execution>
            <id>prefilter-resources</id>
            <phase>generate-resources</phase>
            <goals>
              <goal>resources</goal>
            </goals>
            <configuration>
              <outputDirectory>target/generated-resources</outputDirectory>
              <resources>
                <resource>
                  <directory>src/main/resource-templates</directory>
                  <filtering>true</filtering>
                </resource>
              </resources>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
    <filters>
      <filter>${ffile}</filter>
    </filters>
    <resources>
      <resource>
        <directory>src/main/resources</directory>
      </resource>
      <resource>
        <directory>target/generated-resources</directory>
      </resource>
    </resources>
  </build>
  <dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>test</scope>
    </dependency>
  </dependencies>
  <properties>
    <ffile>filter.properties</ffile>
  </properties>
</project>

thing is this part:

<resources>
  <resource>
    <directory>src/main/properties</directory>
    <filtering>true</filtering>
  </resource>
</resources>

is completely ignored. Instead for both maven-resource-plugin executions (the one in generate-resources phase and the default one) this config is used:

<resources>
  <resource>
    <directory>src/main/resources</directory>
  </resource>
  <resource>
    <directory>target/generated-resources</directory>
  </resource>
</resources>

which of course breaks the whole idea.

Is this a bug or a design decision. In latter case is there any equivalent approach I might take?

Issue Links

• is related to: MCOMPILER-13 New Mojos for compiler and jar plugins to allow alternate jars