Mark, thank you for such quick answer, even if it's on Maven rather than AppFuse!.
mraible wrote: > > On 10/9/07, Florian Kirchhoff <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I have a question regarding the use of jdbc.properties. When I run my >> tests, >> I see that the placeholder values in src/test/resources/jdbc.properties >> get >> replacted with the values in pom.xml before the file is deployed to >> target/test-classes. > > This is done by the "maven-resources-plugin", which isn't listed in > your pob.xml because it automatically runs in the process-resources > phase. > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > If you look in pom.xml, you'll notice that filtering is on for > resources. The properties that are substituted are taken from the > <properties> section. > > http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html > >> >> But when I run the install goal, then src/main/resources/jdbc.properties >> doesn't get the same treatment and is just copied to target/classes as >> is. > > That's strange - it should have the same behavior since the same > lifecycles are still fired. > It was because my test resources were filtered but my main resources were not. I added <resources> <resource> <directory>src/main/resources</directory> <filtering>true</filtering> </resource> </resources> to my pom and I was good to go. Thanks again. Florian -- View this message in context: http://www.nabble.com/When-are-values-in-jdbc.properties-substituted--tf4595051s2369.html#a13120405 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
