We're setting up CVS on a Solaris box, and we're using it for a Java/JSP implementation.
what's the ideal way to deploy CVS in a web-development context using Apache/Tomcat. How would a web-based implementation of CVS be different than a software build type CVS implementation? Noel adviced to not have a shared working directory for different developers, but what if you simply need to change one minor thing on a JSP page, then save it and refresh the browser to see the change on a development machine? Would that entail a checkin then a commit, thus forcing all other developers to update their working directories? Moreover, do all developers set up a working directory in their home directory, then a virtual server to point to that location, and when they're done w/ their "piece" of the site, do they commit it to the main trunk? Should all developers get a "branch" ? Anyone have any experience deploying CVS for web implementations? Thanks in advance..... Paul __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
