I think you're orbiting the point here... let me talk you down ;-) James proposals are seperate bits of the repository, they are not actually cvs branches. In particular IMAP is a set of extra classes, but more importantly it also contains replacements for one or more classes and configuration files, forks of them.
In theory to build a proposal you should check out the HEAD (the general, default, current code) build james then build the proposal. I can't speak for IMAP but build -f proposals/imap2/build.xml should work if the build process is correctly set-up James may not run at all if IMAP isn't up to date with relevant changes to the main project code, or the imported avalon classes. (good luck) d. > -----Original Message----- > From: Steve [mailto:[EMAIL PROTECTED]] > Sent: 10 December 2002 22:34 > To: James Users List > Subject: Will compiling a cvs branch mean losing main branch code? > > > I am not familiar with the intricacies of cvs. I have tried > to gleem some understanding of the "branches" concept > by eves-dropping on the -dev list. Please forgive my > neophyte question: > > I see that there has been some work done on the imap > support in the imap2 branch under proposals. I would > like to "play" with it a bit to get an idea of how far it has > come. I have read in earlier posts that I might be able > to compile this by entering > > build -f proposals/imap2/build.xml > > However, I understand that several improvements have > been made in the main branch since this imap2 devel- > opment began. Are branches "in addition to" the root > branch? Or am I getting a snapshot of where pop and > smtp was when the recent imap efforts began? > > (I hope this question even makes sense) > > Thanks! > > Steve B. > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
