ok
after good reading I see the potential issue in using profiles to put
different filters file:
...
<build>
<filters>
<filter>src/test/filters/dico.properties</filter>
</filters>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
<profiles>
<profile>
<id>profperf</id>
<build>
<filters>
<filter>
src/main/filters/perf/dico.properties
</filter>
</filters>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
<activation>
<property>
<name>profperf</name>
</property>
</activation>
</profile>
<profile>
<id>profprod</id>
<build>
<filters>
<filter>
src/main/filters/prod/dico.properties
</filter>
</filters>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
<activation>
<property>
<name>profprod</name>
</property>
</activation>
</profile>
</profiles>
...
Is it the good way?
--
View this message in context:
http://www.nabble.com/properties-file-valorization-during-integration-tf1850139.html#a5067417
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
