ANT accomplishes the objective by reading separate properties file for each
environment
http://ant.apache.org/manual/CoreTasks/property.html
<property environment="env"/>
<echo message="ANT_HOME is set to = ${env.ANT_HOME}"/>
and then use the environment variable ANT_HOME as the arbiter of which
property file to use e.g.
<property file="${env.ANT_HOME}/.ant-global.properties"/>
ping [EMAIL PROTECTED]
for follow-up questions..
Martin--
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <axis-user@ws.apache.org>
Sent: Thursday, December 20, 2007 6:25 AM
Subject: RE: Name Changes For Development Test and Production Deployments
Hi Peter,
I think this problem is beyond Axis and Axis2 and is more on project
base. I know that maven has built-in support for different environments
using profiles to support this. For ant there are alternatives but I
don't exactly know how to deal with this. I think they make use of extra
tasks for different environments.
Good luck!
Sietse
-----Original Message-----
From: Peter Hargreaves [mailto:[EMAIL PROTECTED]
Sent: 20 December 2007 11:16
To: axis-user@ws.apache.org
Subject: Name Changes For Development Test and Production Deployments
We would like to deploy our service under different names within the
Axis2
application:
1) DevWebService connected to a development database.
2) TestWebService connected to a test database.
3) ProdWebService connected to a production database.
The problem is that renaming a service seems to have many consequences,
so these different versions of the same service have many differences
other than just the database connection.
How do other people run different versions of the same service?
Is there a simple way to do renaming for this purpose?
Any ideas please?
Pete.H.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
