Anybody interested in CVS should take a look at the online version of Karl Fogel's book:
cvsbook.red-bean.com It helped me get up and running with CVS in about a day. Thanks, --jeff ----- Original Message ----- From: "Ralph Einfeldt" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, November 20, 2001 7:54 AM Subject: AW: CVS > See below: > > > -----Ursprüngliche Nachricht----- > > Von: Laurent Michenaud [mailto:[EMAIL PROTECTED]] > > Gesendet: Dienstag, 20. November 2001 16:12 > > An: Tomcat Users List > > Betreff: RE: CVS > > > > > > We prefer to use cvs rather than Ms SafeSource. > > > > I was asking still questions : > > - What's better ? a repository for each project or a module for > > each project ? > > We don't use either, the projects are simple sub directories under > one root in the repository. > > > - Is it a good idea to use CVS for binary files ? i was thinking > > about class files, and all the jpeg/gif files... > > In general yes. But I would just put class files in the repository > if they are not build from sources. And make shure that you > use/configure > cvs correct to handle binaries. (Otherwise you might expierence some > surprises.) > > > - What would do the site construction script ? pre-compile the jsp and > > the servlet maybe ? Have u got examples of script that i could see ? > Checkout all needed files for a given tag. > Compile the java classes, make a jar of them, fill a test database..... > > In our environment we have several files that are the same over the > project that are placed outside the project directory. Our installation > script copies these files in the deployment site where our webserver > runs > and mixes them withe project specific files. > > We have automated the setup of a webserver, so that we can setup a new > instance of the same project in few minutes once we have defined all > configration parameters. (Even the initial setup of new project > doesn't take much longer) > > This we use to build the web server up to several times a day. > > The examples won't help you much because they still work with good old > JServ. > > > - I think we will need differents branches : > > - one for each stable release > > - one for a beta developpement but fonctionnal, few bugs. > > - one for an alpha developpment, used to backup the progress > > I wouldn't do to much branches. Just use Tags to mark this versions. > > > works( i am hesitating > > here with a branch for each developper ). > > A clear NO! to this approach. > > > For example, a developper that has not finished a work at the > end > > of the day will update the alpha branch. > > If a developer isn't ready, the he shouldn't checkin. So the your > alpha branch is just the developers workplace in my world. (What do you > win > with this checkin ?) > > > A developper will update the beta branch when he thinks his > > source > > is quite ok. > > The stable release will be built after hard testing of the > > global > > application. > > > - Last question : which utils do u use for cvs ? there is wincvs, i've > > seen webcvs too. > > Are there any others ? > We use WinCVS, XEmacs and the command line interface > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
