Each user defining this property through a profile in his/her settings.xml is the way to go. However, best practice is to have default values of the properties defined in the project's pom. The project should NOT rely on configuration in settings.xml.
/Anders On Thu, Nov 12, 2009 at 04:17, Jeff French <[email protected]> wrote: > > I'm finally getting the chance to migrate some of our m1 projects to m2, > and > am wondering about the m2 way to do the following. > > During our m1 test phase we replace macros such as @db.host@ in some > config > files. The maven.xml file has a goal which defines some filters, and > individual developers can set properties such as db.host in their > build.properties file in the project root. > > I'd like the same end result in m2 - that developers can use their local > database for testing. After Googling and looking at examples, it seems that > defining a profile in settings.xml might be the way to go, but that seems > like overkill for the simple macro replacement I'm trying to do. Is there a > better way to handle this in m2? > > Thanks for any pointers. > > Jeff > -- > View this message in context: > http://old.nabble.com/Personal-property-substitution-in-m2-tp26312742p26312742.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
