I think it is easier to make these as separate projects and they all depends
on the App.jar artifact.
The App.jar artifact does not contains ANY configurations for a environment,
it is stored in the separate
projects like this:
(
These projects takes the App.jar
file and add the properties etc
f
: 'Maven Users List'
Subject: RE: M1 - More than 1 artefact
I think it is easier to make these as separate projects and they all depends
on the App.jar artifact.
The App.jar artifact does not contains ANY configurations for a environment,
it is stored in the separate
projects like thi
Hi Simon,
yes I have encountered the same problem, and the technique we used
where I work, was to have three projects. One for each artifact. We
prefixed the uat project uat_ and the prod project prod_. These two
projects inherts from the dev-project (which we didn't prefix). We set
the source fol
Simon,
We have the same problem. We use one project but three
build.properties files (build.dev.properties, build.uat.properties and
build.live.properties).
In maven.xml we have three top level goals 'dev', 'uat' and 'live',
which source the right properties file. We then use those proper
