Stephen - can you clarify which points you're against? If there are profiles (and filter files) for every environment they deploy to - then yeah, don't do that.
BUT - for example, if there are exactly two (one for dev, defaults in poms, overrides in each person's settings.xml) and one for prod (which inserts OTHER templates to be use by an orchestration system against these "new" templates), then I see no harm - but they'll have to make sure each property is defined (somewhere). On Fri, Dec 21, 2012 at 3:32 PM, Stephen Connolly < [email protected]> wrote: > > http://developer-blog.cloudbees.com/2012/11/maven-profiles-and-maven-way.html > > Please don't do maven the way you are doing it > > On Friday, 21 December 2012, Niranjan Rao wrote: > > > Greetings, > > > > We have bunch of profiles and corresponding resource filtering which all > > works great. One frequent problem that we encounter team members often > > forget to add new values in profile/filter property file of other > profiles > > than the one they are currently using. Naturally results are disastrous. > > Normally we can find quickly which property is not filtered correctly > and > > fix it but this is tedious. > > > > I am wondering if there is any way to catch missing properties at build > > time. That is when maven sees a property definition during filtering > phase > > which has variable declaration and could not locate the value, can it > raise > > the error and let the build fail? > > > > Thanks, > > > > Niranjan > > > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
