> [EMAIL PROTECTED] wrote:
> >
> > Hi,
> >
> > Is it currently a bad time to check out from CVS?
> [SNIP]
> >
> > Lots of stuff has moved around, eg org.apache.velocity.Context is now
> > org.apache.velocity.context.Context.
[snip]
>
>It could be because I DID IT OVER 2 MONTHS AGO ON JANUARY 3...
>
> :)
>
> geir
Whoops, guess who feels dumb now :) Sorry.. although I should note that the
solution is *not* always just "delete the bin directory" as Jon said.
It's possible for the repository to change such that sandboxes *cannot* update to
the new state, and that's what happened to me:
[jeff@kermit ~/jakarta-velocity]$ cvs -q up -A -d -P src/java/org/apache/velocity/
cvs server: cannot open directory
/home/cvspublic/jakarta-velocity/src/java/org/apache/velocity/injector: No such file
or directory
cvs server: skipping directory src/java/org/apache/velocity//injector
cvs server: cannot open directory
/home/cvspublic/jakarta-velocity/src/java/org/apache/velocity/parser: No such file or
directory
cvs server: skipping directory src/java/org/apache/velocity//parser
cvs server: cannot open directory
/home/cvspublic/jakarta-velocity/src/java/org/apache/velocity/visitor: No such file or
directory
cvs server: skipping directory src/java/org/apache/velocity//visitor
Perhaps someone edited the CVS repository by hand to prune directories? Anyway,
the fix is to blow away the sandbox and start again.
thanks,
--Jeff
