Hi Angelo,
With maven, you can use profile to define a build behavior.
In your case, you can define a resources folder per environment
(production, testing, etc) and create a profile per environment.
In the profile, you define the corresponding resources folder.
After you can do something like:
mvn -Ptesting install
or
mvn -Pproduction install
You can "tag" your SA using a classifier. Your profiles can use
classifier to include the profile name in the SA file name.
Regards
JB
angeloNZ wrote:
Hi,
I'd like to get some recommendations as how best to build the SA for
different environments (integration, system test, production). For example,
I want to have different property files for system test and production and I
want my xbean.xml for my Binding component definitions to be able to use the
appropriate property file as the SA is being built. I already know how to
define a propertyConfigurer in my xbean to include a property file and have
some consumer/provider attributes read off the file. What I'm interested in
is, when building the SA, how do we tell it to say, read off from the
production property file? Is this something we can indicate when running
the mvn install command?
The xbean.xml should also have namespace definitions that should match the
namespace from the wsdl file of your external web service. I know from
trying that you cannot read off the namespace value from a property file
from the main <beans> element. This does not work:
<beans xmlns:x="${namespace.from.propertyfile}" ...>
how do we deal with namespace definitions when building the SA dynamically?
do we need to have xbean definitions per environment?
Thanks for your inputs.
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
[email protected]
[email protected]
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
