--- Paul Tomsic <[EMAIL PROTECTED]> wrote: > what's the ideal way to deploy CVS in a > web-development context using Apache/Tomcat.
I've already given my opinion on this so I won't elaborate more on it. > How would a web-based implementation of CVS be > different than a software build type CVS > implementation? IMHO, the difference is that developers need to install their product into a development environment (rather than using the built product straight out of the working directory). > 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? As I said above, developers need to install into their environment to test out their changes. If they checkin without testing, like in all other projects, they risk broken builds, bugs, ... > 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? Unless I'm missing something, yes. > Should all developers get a "branch" ? Since the task is more interesting than the developers who worked on it, I personally prefer task branches over developer branches. Moreover, CVS doesn't handle seemlessly remerges onto the same branch as would happen with developer branches. > Anyone have any experience deploying CVS for web > implementations? I think the build and deploy process is independent of the source control system. Noel __________________________________________________ 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