Re: [stellation-res] Release vs. Trial

["Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx>]

On Mon, 2002-12-23 at 22:15, Jeffrey Howard wrote:
> Hello,
> 
> After installing the stellation core binary distribution (build
> 2002-12-22), I downloaded and installed the client feature for
> Eclipse.  In setting up a project to be shared, the client feature
> allows one to test the settings used to set up a repository.  When I
> did so, Eclipse became unresponsive.  I believe it was waiting for
> some reply that never came.

There are two pieces to what you're seeing.

First, you're encountering a rather frustrating known bug, where a bit
of code that's got a timeout isn't timeing out.  

Second, you're encountering a build artifact. I'm not sure if it's quite
fair to consider it a bug. Here's a quick explanation:

One of my big worries building the system was that once we started
self-hosting, we'd accidentally use an untested development version of
the CLI client to access the production repository. So I added the
tag: it's purpose is to provide a hard-coded constant in the executable
of the client, and to require the value of that constant when the client
is run to match a value written into the repository when it was created.
The tag is always set to DEBUG, except when you're building a version
for installation with a live server, in which case it's set to RELEASE.

In the official builds of the server, the ant scripts set the tag to
RELEASE, since it's building a release version. Since the Eclipse
plugin isn't yet stable enough for production use, he compiles it with
the tag set to DEBUG. 

So your production server is being contacted by a debug client, and it
refuses the connection. Unfortunately, there's another bug in the
comm layer, which I haven't had the time to track down, which causes
errors like tag mismatches to result in a deadlock in the client. 

Nothing will be harmed by manually changing the tag value in
the database to DEBUG. The one problem that you'll have is that the
version of the CLI client installed by ant was compiled with the tag
as RELEASE - so the CLI client won't work. 

I think the best workaround is probably to do a build in the source
directory, and take the jar generated for running tests (which run
with DEBUG), and copy it to the installation jar over the old jarfile. 
The only difference between the jars should be the value of the tag.
Then recreate the repository using the new jar, and everything should
match.

	-Mark

-- 
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center  
*** The Stellation project: Advanced SCM for Collaboration
***		http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx  ------- Personal Email: markcc@xxxxxxxxxxx