That sounds like a defect. If it is not already in JIRA, please help out and log it.
In the interim, have you tried creating an always-active profile with a property element? That might work, but I'm not certain. Eric On 9/5/06, fagfa <[EMAIL PROTECTED]> wrote:
We have a parent project which contains several J2EE subprojects, such as web, ejb, ear, etc.. In the parent POM, a property "db" is defined, whose default is "hsql", for example. Build for various databases can be switched by specifying commandline, "mvn -Ddb=mysql", or changing "db" property directly. In our sub projects, there are some resource files that depend on this "db" property and we hope these resource files are properly filtered during the building. If I just change "db" property in parent POM file, everything works perfectly. But when I specify "-Ddb=mysql", the resource files are filtered, but still by the properties in the parent POM, not from command line. Based on my understanding, property specified in command line should precede elsewhere specified, which is NOT happending here. Any ideas? Thanks, fagfa -- View this message in context: http://www.nabble.com/Property-overwriting---resource-filtering-for-sub-project-tf2222400.html#a6157180 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Eric Redmond http://codehaus.org/~eredmond Don't mistake the fact I make this look easy to mean that it is - at all - easy.
