> Profiles are used to just swap between configurations, run plugins that > normally don't run, etc. > > 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 already).
Well, the objective is to eventually have all our projects configurable like this. We have a dang large number of projects so keeping each one down to one file would probably be wise. Besides I don't want the devs having to look in more than one place for config of one project. Ideally this would be two projects, but that is not my call. I just have to roll with it. ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
