Just curious: where do you need this for? If you want plugins / dependencies always to be active, you could add them in the pom directly, then they don't need to be in a profile. Couldn't you simply define them directly in the pom instead of adding it withing a profile?
2010/1/14 Mark Hobson <[email protected]> > Hi there, > > Is there a better way of always activating a profile, unless > explicitly deactivated, than using a dummy property activator? For > example: > > <activation> > <property> > <name>!dummy</name> > </property> > </activation> > > I can't use activeByDefault since I want the profile to be activated > even when other profiles in the pom are active. > > It could be worth introducing an always active activator, something like: > > <activation> > <active/> > </activation> > > I'll raise an issue if no-one objects. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Squins | IT, Honestly Oranjestraat 23 2983 HL Ridderkerk The Netherlands Phone: +31 (0)180 414520 Mobile: +31 (0)6 30413841 www.squins.com http://twitter.com/keesvandieren Chamber of commerce Rotterdam: 22048547
