Hi John! On Friday, November 29, 2002 17:01, Morrison, John wrote: > > From: Ivan Mikushin [mailto:[EMAIL PROTECTED]] > > > > Oops! It was my bad CVS update command (forgot the -d option > > after update). > > Yeah, the update -d option creates any missing directories, things > really go to pieces if you miss this! (I've done it before). > > > Now it builds OK :)) > > > > BTW, in the docs it says one should update his own local copy > > from the CVS > > with <code>cvs -z3 update -d -P</code> which generates an > > error. The docs > > MUST be updated with the correct command which (I think) is > > <code> > > cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic -z3 > > update -d -P > > </code> > > No, once you've done a checkout, cvs references > <project>/CVS/Root > > for the :pserver:... information unless you override it with the first > -d.
Here's what I get from cvs -z3 update -d -P: cvs update: in directory .: cvs update: ignoring CVS/Root because it specifies a non-existent repository /home/cvs cvs update: No CVSROOT specified! Please use the `-d' option cvs [update aborted]: or set the CVSROOT environment variable. Maybe this is because I never did the checkout: just downloaded the CVS snapshot and then updated it? > > Sorry for having disturbed you, the MIGHTY COCOONERS with > > such a little bug :) > > Huh? Is this a joke or are you taking the micky? :) I don't know what "to take a micky" is, but sometimes there is no reply, even when I'm talking about serious things. Though, when I'm persistent and doing it in creative ways I receive the response (like above (of course, it's a joke, <joke>should have marked it up as was recommended by someone a while before in this list</joke> :)) > > Expect more soon: there is a major classloading issue which > > prevents people to > > put the cocoon libs (pretty *much* of stuff, I'd say) into the shared > > directory for all webapps and only put their own stuff into > > their webapps' > > WEB-INF/classes and WEB-INF/lib > > True, if this is the case, it probably ought to be fixed. I'm trying to solve it now, working out a patch. But if I'm stuck I'll beg for help 'cause *this* is a problem that stops my Cocoon 2.1 hosting project. Cheers, Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
