[stellation-res] Eclipse Client Load Revision (Checkout)

[Jeffrey Howard <jhoward@xxxxxxxxxxxxxxx>]

Hi there,

Hopefully you're all on vacation by now.  :) I have a question based
on working with the Eclipse client feature for when you get back.  I
understand that publishing changes out to other branches is not yet
implemented.  In my toy project, I have some work in my sandbox branch
that I want to publish to the main branch.  From reading the
documentation for the command line tools, I gather I can achieve this
effect by checking out the main branch and then merging from the
sandbox into the main branch.

I think I ran into a bug when trying to check out a branch (in the
Eclipse right-click menu, the action is called "Load Revision").  The
action returns without displaying a dialog box of any kind.  A
NoSuchElement exception is thrown by the StringTokenizer.nextToken()
call in the ScmFacade.getBranchItems() method.  (I'd provide the stack
trace, but I have a few debugging statements in there now that would
throw off the line references.)

The relevant segment of code is around line 412 or so of ScmFacade.
There is a loop while (versionIter.hasNext()) which invokes the
StingTokenizer's nextToken() method on a String of version information
retrieved from the server.  The delimiter being used to tokenize is
the tab character '\t'.

When I look at the debug log produced by the server, the VersionString
looks in order:

<VersionString string="My Project Name	jhoward-sandbox	0	jhoward	Mon Dec 23 18:18:38 EST 2002" />

But when I print altered the in ScmFacade to print out the string just
before it's tokenized, the tabs have been replaced by spaces.  Thus
the tokenizer only sees one (long) token and throws a
NoSuchElementException when the attempt is made to retrieve more
tokens.

Just to get all the version information out of the way, I'm using
Redhat Linux 7.3 and Sun's JDK 1.4.0.  I'm running Eclipse M4, and the
12-22-2002 build of the Stellation core.  Lastly, I'm running the
0.0.6 version of the Stellation Eclipse client, modified only by the
insertion of debugging printlns after discovering this exception being
thrown.

Is this a known problem?  (I checked bugzilla and didn't see it.)  If
not, any good guesses as to where I should look first?  It looks like
the messages between the client and server are being written and read
with PrintWriters and PrintReaders, which should understand the
difference between a space and a tab.  Does it seem like sound
reasoning that I should start looking at whatever code or class
library is parsing the XML?

Thanks,
Jeffrey