Having different "flavors" of your artifacts, depending on which environment you build for is not recommended. In Maven, a specific artifact defined by GAV (i.e. a specific version of your artifact) cannot (should not) change. We've had numerous discussions regarding this on the list. It simply isn't the Maven way. What you should do, is to try to keep your configuration separated from your binaries. And then create separate artifacts (either through classifiers or different projects) for each environment. And in your build process, by default, you build them all.
/Anders On Mon, Jun 21, 2010 at 14:58, Mariyan Nenchev <mnenc...@trinitascapital.com > wrote: > Hi, > > I have a huge java project with several modules. The build is based on > maven. There are many parameters, that are used in the project and i have > placed them in the database. They are environment specific (for example > parameter x has value1 for TEST, value2 for UAT, value3 for PROD so on..). > I > want to create 3 different configurations about these 3 environments. And > tell something like project_root$mvn install configuration1 -> this builds > me the whole project by using parameters setuped for UAT for example. > > Is there any way to do this with maven? > > Regards. >
