|Using J2EE 'server' as a pre-deployment test environment [message #207277]
||Mon, 21 January 2008 16:46
| John J. Barton
Registered: July 2009
I've tried various combinations of configurations in the Server function |
of WTP without finding the one that would be ideal for me.
I want to run with eclipse against a Tomcat installation, test the
service, then stop the server and do svn commit on the Tomcat tree to
commit the new deployment. On the customer machine I just want to svn
update to get the new version. This gives minimal time on the customer
machine and good overlap between test and deploy environments.
I tried using server settings "Use Tomcat installation", but something
that WTP does corrupts the directory that svn needs. The tree cannot be
committed after WTP works on it.
The best, and it's not very good, that I have is to test, go over to
Tomcat install, delete the servlet, go back to eclipse, export .war,
commit svn. At least the customer site has the update-run experience.
I suppose I could go back to uploading war files in to the test and
customer machines, but that is so tedious...
Any other approaches/ideas?