maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EJ Ciramella" <>
Subject RE: Deployment Properties file
Date Thu, 18 Feb 2010 19:38:20 GMT
Profiles are used to just swap between configurations, run plugins that normally don't run,

Stuff you'd like to be able to switch on and off.

If your goal is to just load properties, that seems like a good approach.

Now if you had a properties file for each server type, then you'd put each property file loading
configuration in a profile devoted to that app server (but from what I can tell, you get that

-----Original Message-----
From: Jim Collings [] 
Sent: Thursday, February 18, 2010 2:23 PM
To: Maven Users List
Subject: Re: Deployment Properties file

>> all have their stuff in different places.  What I want is a properties
>> file that the dev can stash in his home directory which will be read
>> by Maven to establish installation parameters and JVM options for each
> Maybe use settings.xml in user home dir? Otherwise this calls for a profile.
> Wayne

Profiles? Aren't those used for different platforms?  I think you
mistake my meaning. We have a project that has two subcomponents, one
of which runs on a full J2EE container, Weblogic and the other which
runs on Sun Webserver 7.

BTW, this seems to work OK:


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message