With version 2.5 you are now able to build your own custom resources filter(s).
Your custom resources filter classes must implements org.apache.maven.shared.filtering.MavenResourcesFiltering.
Your custom resources filter classes must be marked as a Plexus Component. Below a sample with a roleHint itFilter.
/** * @plexus.component role="org.apache.maven.shared.filtering.MavenResourcesFiltering" * role-hint="itFilter" */ public class ItFilter implements MavenResourcesFiltering
Then you must activate in your build the mojo which will scan javadoc annotations to transform thoses to plexus component metadata.
<plugin> <groupId>org.codehaus.plexus</groupId> <artifactId>plexus-component-metadata</artifactId> <version>1.7.1</version> <executions> <execution> <goals> <goal>generate-metadata</goal> </goals> </execution> </executions> </plugin>
Your classes must be available in the maven-resources-plugin classpath, this can be done with adding your artifact to the plugin dependencies.
<project> ... <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <version>4.0.0-beta-1</version> <configuration> ... </configuration> <dependencies> <dependency> <groupId>custom resources filters artifact groupId</groupId> <artifactId>custom resources filters artifact artifactId</artifactId> <version>custom resources filters artifact version</version> </dependency> </dependencies> </plugin> </plugins> ... </build> ... </project>
You must now declare you custom filter in the plugin. mavenFilteringHint must respect same syntax as your Plexus Component roleHint.
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <version>4.0.0-beta-1</version> <configuration> ... <mavenFilteringHints> <mavenFilteringHint>itFilter</mavenFilteringHint> </mavenFilteringHints> </configuration> ... </configuration> </plugin>
And that's it !