yes, which is a best practice :-) It can work like that too : - In your pom you put the distributionMgt with the property - in your settings you create a profile with this property but instead of using an activation activateByDefault you define it in activatedProfiles list. It will work but I think Maven 3 will write a warning because your build is dependent of your environment (which is wrong).
In Maven 3 we didn't touch to settings nor pom but we have always in mind to propose more interesting features in a near future. Like mixins which will allow to integrate several parts of pom or settings Arnaud On Oct 4, 2010, at 9:39 PM, Phillip Hellewell wrote: > On Mon, Oct 4, 2010 at 1:36 PM, Phillip Hellewell <ssh...@gmail.com> wrote: >> 2010/10/4 Arnaud Héritier <aherit...@gmail.com>: >>> Wrong :-) >>> Let me try to explain ... >>> Your approach to allow to override this parameter using a property is good. >>> I'm doing it to validate a new version of my repository manager and so on. >>> But how you are doing it is wrong. >> >> I didn't know I could define properties outside of a profile section. >> Let me give it a try... > > Crap, you can't do that in a settings.xml. To do it outside of a > profile section it has to be in a pom, so that leads me back to having > to use a parent or "corporate" pom :( > > Phillip > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
