Hi Ian,
[Warning: Following is untested.]
I don't know about the best way, but I think you should be able to set
up an <execution> for each of the filterings you want to do, something like:
<build>
...
<plugins>
...
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>one</id>
<goals><goal>resources</goal></goals>
<configuration>
<resources>
<resource>
... <!-- same syntax as <build><resources>? -->
</resource>
</resources>
<filters>
<filter>
... <!-- same syntax as <build><filters>? -->
</filter>
</filters>
<outputDirectory>
${project.build.outputDirectory}/one
</outputDirectory>
</configuration>
</execution>
<execution>
<id>two</id>
...
</execution>
...
</executions>
</plugin>
...
</plugins>
</build>
Steve
Ian Rowlands wrote:
> Just wondering what is the best way to do "multiple" filters over a set of
> files. The context of the question is:
>
> I have a set of configuration files, and 6 different environments they
> could be deployed in. There is one properties file for each environment.
> I'd like to generate the configuration files for all of the environments
> during the build, stored in different sub-directories. Then when I deploy,
> I'll extract the set of files which is appropriate and deploy them. But I
> need to have the files for all environments upfront.
>
> From my understanding of maven filtering, I can only filter the files once.
>
> Any ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
