activation is king ;) The reason why it got removed is obvious: you needed to know exactly what goes into it. Without that info you sometimes could not even compile your project.
What you can try nowadays is to create profiles (maybe in your parent pom) and have them activated via a system property. LieGrue, strub ----- Original Message ----- > From: Jochen Wiedmann <jochen.wiedm...@gmail.com> > To: Maven Developers List <dev@maven.apache.org> > Cc: > Sent: Thursday, May 10, 2012 9:40 AM > Subject: I'm missing profiles.xml > > Hi, > > just opening a several years old project, which was written for Maven > 2 before 3.0 and is making heavy use of profiles.xml. > Reminds me how much I am missing this feature: Local profiles used to > be the most obvious, easiest to use place for > local customizations like configuring a database URL or stuff like > that. My own appreciation of Maven became significantly > lower with the removal of that feature. > > Now, I am not asking to readd that feature, but I am wondering whether > it wouldn't be possible to reintroduce it just for me by enabling a > Maven extension or plugin that supports it. > > Any hints on how I could implement that? > > Thanks in advance, > > Jochen > > > > -- > "Bildung kommt von Bildschirm und nicht von Buch, sonst hieße es ja > Buchung." > Dieter Hildebrandt > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
