My first diagnostic was wrong.
Here is my config :
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>dev</id>
<goals><goal>resources</goal></goals>
<configuration>
<outputDirectory>${basedir}/src/main/properties/dev</outputDirectory>
<filters>
<filter>${basedir}/src/filters/dev.properties</filter>
</filters>
</configuration>
</execution>
</executions>
</plugin>
outputDirectory is set as expected, but not filters.
Using debugger, I wen into CollectionConverter.fromExpression( .. )
with configuration =
"<filters><filters>D:\projets\pnm\pnm/src/filters/dev.properties</filters></filters>"
The configuration.gatValue( null ) is expected (but maybe I'm wrong) to
return the configured value... for a strange reason, the
configuration.domattribute has its value set to the expression "${
project.build.filters}" and does not return the childlist...
What's wrong ?
Is this related to expression vs default-value ?
Nico.
2008/2/14, nicolas de loof <[EMAIL PROTECTED]>:
>
> Hello,
>
> I need to generate configuration fils for muliple environments
> (dev/test/prod) in the same build, to get packaged in my assembly.
> The templates files are in my resources directory, and I have 3 filters
> files in src/main/filters
>
> I'd like to run the resource plugin 3 times using <execution>, with
> configuration changed to use the 3 filters files
>
> ... but the filters parameter is set as expression="${
> project.build.filters}"
>
> Is there any way to set <configuration> to override this expression ?
> Using <project.build.filters>MyFile</> has no effect.
> Why is expression used for plugin parameters ? Why not use default-value,
> so that user can override whene needed ?
>
> Nico
>
