On Mon, Mar 25, 2013 at 7:14 AM, Jörg Schaible <joerg.schai...@gmx.de>wrote:
> Eric Kolotyluk wrote: > > > > > On 2013-03-25 3:49 AM, Jörg Schaible wrote: > >> Hi Eric, > >> > >> Eric Kolotyluk wrote: > >> > >>> I have two development environments: work and personal. > >>> > >>> I am trying to set up my projects so that the POM knows which profile > to > >>> activate, but it seems you cannot put <activeProfiles> in a POM, only > in > >>> a settings.xml file. Is there some reason for this? > >>> > >>> Is there some other Maven way to do what I want to do? How do other > >>> people separate work development from personal development? > >> What's the problem with it? If you active a profile in the settings.xml, > >> you can use this profile (i.e. a profile with same name) also in your > >> POMs, you don't need an activation anymore. > > actually I don't get why a separate VM is preferable to a second > settings.xml in this case - if we still only talk about Maven ;-) > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > Personal preference. For me it makes more sense to just work in a specific role or environment for all my work. Having to manage multiple settings files leads to complexity, mistakes, and frustration. I don't want to have use Maven with more options than I need to. I really believe in convention over configuration, and multiple settings.xml files violates that principle. Cheers, Eric
