[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [stellation-res] Missing stuff on Stellation Server
|
Jonathan,
The server was down Monday-Wednesday this week (there was a hardware
problem with the backup unit, and apparently the resulting hassle
kept those involved from remembering to restart the Stellation server
after the backup finished :(
Mark just told me that it's up now, and I'm about to start merging
the current repository version into my local workspace. Once that's
done, I will check everything into the server, check out into a
clean workspace, verify that things build and add missing files
as needed.
Note that stellation.scm.model and stellation.scm.ui do
not currently build in my local workspace, for reasons known but
slightly time-consuming to fix. My plan is to
(1) check in buildable code for the CLI and the Stim task
management stuff, and then
2) fix the build-related issues for Eclipse CM client.
You should be able to get moving again once step (1) is done,
without waiting for me to complete (2).
I will post a note when (1) is done.
Regards,
Jim
At 02:58 PM 8/14/2003, Jonathan Gossage wrote:
<snip>
>
> I'll try to fix up the rest of the missing/extra file issues
> later today. I'm not sure if I'll have time; if not, I'll
> do it first thing tomorrow. (We're having my daughter's
> 3rd birthday party this afternoon, so I'm a bit busy today.)
>
I notice that there has been no change in the status of the source on the
Stellation server. Is there a problem that is preventing anything from
happening. I have a number of things I would like to get moving on but until
we have an authoritative code base in Stellation, I am not prepared to move.
Or do you want development to continue using the CVS repository for the
moment?
Regards
Jonathan Gossage
--
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
jim.wright@xxxxxxx