hivemind-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <ja...@carmanconsulting.com>
Subject RE: Run modes: Dev, Test, Production
Date Mon, 27 Jun 2005 16:12:31 GMT
Do you mean something like substituting in the database connection settings
(url, user, password)?  HiveMind has SymbolSources which can be used for
this.  You could create a SymbolSource which is based on a property file.
Then, you just substitute in your property file for your specific
environment.  

For this, I usually incorporate Velocity into my build system so that I can
create a file (or files) that is based upon values from my build.properties
file.  That way, any customization goes on in one place, the
build.properties file.  The problem with this is that you actually have to
run the build whenever you want to deploy your project to a new environment
using a new build.properties file specific to that environment, but in my
case, that hasn't been much of a burden.  If you want the code for the
velocity task, let me know.

-----Original Message-----
From: Joel Trunick [mailto:joel.trunick@webifysolutions.com] 
Sent: Monday, June 27, 2005 11:56 AM
To: hivemind-user@jakarta.apache.org
Subject: Run modes: Dev, Test, Production


Does Hivemind have some support for supporting different modes of
operation (ie. Dev, Test, Production), or is there a common paradigm to
support this with HiveMind? I see Ruby supports such a notion, I find it
odd (and time-consuming) that J2EE doesn't support this natively.

Joel


---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-user-help@jakarta.apache.org


Mime
View raw message