Hi,
Our ejb development team works on a centralized server with perforce as
source control, but each of us has our own app server instance running on
the centralized box. I think this is the best-of-both-worlds solution.
Gene
-----Original Message-----
From: Forrest Pan
To: [EMAIL PROTECTED]
Sent: 7/20/01 11:51 AM
Subject: Source Control for EJB Development/Deployment
Hi,
We have multiple developers writing EJBs and we share one development
EJB server. We are using a version control program (MKS), but the
problem is when one developer finished his bean, he has to package it
into the jar file and deploy it on the dev server. This can cause
problems for other developers who are modifying/testing other beans.
Unlike writing desktop applications where each programer can test his
part on his own system, we aren't able to test the software before we
merge our code. Can someone share his/her experience on solving this
kind of problem?
Your help is appreciated!
--Forrest
========================================================================
===
To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
