Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stellation-res] Big changes - should we go for it?

At 12:29 PM 12/15/2003, Mark C. Chu-Carroll wrote:
On Dec 15, 2003, at 11:53 AM, Jim Wright - IBM Research wrote:
At 04:16 PM 12/14/2003, Mark C. Chu-Carroll wrote:

<snip>

If you're proposing to keep N separate Eclipse plugin projects within a single
Stellation SCM project, that's probably fine (modulo a question or two).
If you're proposing something else, please clarify.

That's right - I meant to say all of the Stellation Eclipse plugins as
a single Stellation project in the repository.

The proposed change will significantly impact the Stellation GUI plugin
design:

Actually, it really shouldn't. WVCM is sufficiently powerful and
flexible that by using it, we can actually solve that problem
gracefully!

That's likely true for the final GUI plugin (for WVCM).
However, I was referring to the T-Client plugin, designed to work with
the existing Stellation cient/server/repository code.

My assumption was that the proposed change was w.r.t. the **current** ongoing
work, to _create_ the WVCM implementation.  We're using the existing Stellation
codebase for that work, so I figured I'd need to change the T-Client in order to
support our near-term WVCM effort.

Am I missing something? If not, it still seems that I will need to enhance the T-Client design in order to accommodate the near-term consolidation of multiple
pre-WVCM Stellation projects into a single pre-WVCM Stellation project
comprising multiple Eclipse projects.

- 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



Back to the top