[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Transitional Eclipse GUI Client
|
On Tuesday, October 14, 2003, at 12:03 AM, Jim Wright - IBM Research
wrote:
At 05:51 PM 10/13/2003, Mark C. Chu-Carroll wrote:
How about the easiest solution of all: install a Stellation test
server on your
own machine? The self-hosting server is not for everyone to run tests
of
possibly buggy code against; it's for managing the code for
Stellation! You
*never* run code against a production system - that's the whole point
of the
debug tag on the access point!
Well.... (somewhat lamely)
* My old server / database config disappeared when I upgraded to RH9;
I was hoping
to avoid some install/configure mucking about.
* I'm working on both Windows and Linux, and would like to access a
server from both.
Howzabout I use a test server running on our internal Linux box:
svc.watson ?
Whatever. Just run your own test server *somewhere*.
-Mark
- Jim
On Monday, October 13, 2003, at 05:43 PM, Jim Wright - IBM Research
wrote:
Mark,
Per my earlier post on Oct 1, I'm working on a 'transitional'
Eclipse client.
(See Wiki discussions for details). This involves from-scratch
Stellation
workspace code.
I've just smoke-tested the basic code for accessing the remote
Stellation repository,
and it works (at least w.r.t. retrieving the list of current
projects from the repository).
Now, I need to expand my JUnit suite to create and modify projects,
but there
isn't (yet) a way to programmatically delete projects from the
repository.
This is by design, for safety reasons, but it makes testing difficult
(previously, I tested with a local repository and simply deleted the
test db
between runs - not good here!).
Mark -- how should I handle this? Some possibilties include:
* Create a new project with a different name for each test run.
This will
create a slew of garbage projects (test1,test2, test3 .... testN),
which should
be cleaned up reasonably often, but may be the least-effort
solution...
* Give me admin privileges on the 'stellhost' so I can delete my
test projects as needed.
* Create a separate repository ('client_test'), and give me admin
privileges for that
(to avoid accidental damage to stellhost contents).
* Provide a programmatic way to delete individual projects within a
repository.
What do you think?
- Jim
--
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
_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM Research
*** http://stellation.eclipse.org
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxx
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM Research
*** http://stellation.eclipse.org
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxx
_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res
--------------------------------------------------------------------
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
_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM Research
*** http://stellation.eclipse.org
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxx
