jira-importer commented on issue #257: URL: https://github.com/apache/maven-war-plugin/issues/257#issuecomment-2967856402
**[Elliot Metsger](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=esm)** commented I encountered this bug while attempting to create profiles for development, testing, and production. The difference in these profiles is in specification of the database driver, url, and credentials. If I set up the filtering in the build element in the pom, the filtering works fine and my jdbc.properties file is situated in WEB-INF/classes. If instead, I want the jdbc.properties file in WEB-INF/conf, the same filter applied in the maven-war-plugin behaves as described in this issue, namely, the project.url gets substituted for ${jdbc.url} rather than the value specified for jdbc.url defined in my filter. I am attaching a minimal project that reproduces these observations in my environment (Linux, Maven 2.0.7, Java 1.5.0_13, and maven-war-plugin-2.0.2.jar). I built with the command: ``` mvn clean compile war:exploded ``` I have found a couple of other potentially related issues, MWAR-96 and MRESOURCES-20. I wonder if there is some dependency misalignment in the plugins. So far I have been unsuccessful in building the maven-war-plugin from SVN since I keep getting failures on the tests. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
