Matt, Ben:

Thanks for the additional information - I'm looking forward to setting up my separate development environment tonight. I appreciate everyones comments and suggestions.

BTW, I assume if you make schema changes to your development mysql instance you manually implement(ALTER TABLE etc.) those changes in the production database during the deploy process, yes?

--Jonathan

Ben Souther wrote:

On Thu, 2004-10-21 at 17:42, Matt Bathje wrote:


Jonathan Wilson wrote:


Yoav, Ben:

Thanks for the tips - I think I finally have a grasp on how a real project would be run properly. I already use MySQL, cvs(in a manual fashion), ant(still new) so I'm not that far away. Development Box Question: Is it *inadvisable* to do the development using the same tomcat version, ant and a local mysql database on a Windows XP box versus the production server which is a linux box? I'd like to start using an real IDE(Eclipse or Netbeans) and having everything on my XP box sounds doable.

Thanks for all your help.
--JW



I can't help with what is advisable or not, but I can tell you that this is exactly what I do with very few problems. My development machine is Windows with local mysql/tomcat/ant/etc. (and eclipse) while my test/live environments use linux.

The one thing I do make sure of is that the versions of mysql/tomcat/ant/jdk/etc. all match between my dev machine and my test/live environments.


Matt




For us, it is advisable because we ship our app to customers who run it
in different environments. Developing, and testing on multiple OSs helps
to insure that there are no platform dependent bugs in there. I'm doing
the opposite though - developing on a Linux workstation and QAing on a
windows box.  I would guess that the majority of J2EE apps are developed
on windows boxes and then tested and deployed on Unix/Linux.

I would advise getting your test environment and your production
environment as close to identical as possible.

-Ben





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Reply via email to