filtering is such a ant way of thinking...
why not properly export configurable entities and perhaps drop the environment
configuration into that environment...
for example you could export specific database settings and load them via
spring property placeholder from the classpath... put the properties into a
jar thats in the tomcat server lib... so all applications in that environment
get the same config on the classpath...
you can then get proper change management on you environmental configurations
by releasing them using the release plugin
On Wed, 05 Dec 2007 08:11:46 Mick Knutson wrote:
> I have a local profile in my settings.xml that is activeby default. I am
> trying to solve:
>
> I want to switch filters based on environment:
>
> <filters>
>
> <filter>${projectRoot}/src/main/filters/filter-${env}.properties</filter>
>
> <!--<filter>${projectRoot}/src/main/filters/filter.properties</filter>-->
> </filters>
>
> SO I would like to keep local as the default:
>
> <profile>
> <id>local</id>
> <activation>
> <activeByDefault/>
> </activation>
> <properties>
> <env>local</env>
> ....
>
> Then if I add -P dev7777 I want to then have Maven override this:
>
> <profile>
> <id>dev7777</id>
> <properties>
> <env>dev</env>
> ....
>
> Is this the proper way to do this for multi-module project?
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
