Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[stellation-res] Status Report (Transitional Client) 
I've just checked in a new version of the t-core code.  This checkin affects
the tclient branch of org.eclipse.stellation.scm.model.
The t-core for the new Eclipse GUI client is now passing all of my tests. These include * checking in various parts of the stellation.stim codebase, in several passes (>100 files) 
* deleting files (singles, groups, folders) and checking in results
* moving and renaming files (to existing/newly created target folders) and checking in results 
* Repeating the above in various combinations  (for a total of 6+ revisions)
* checking out the resulting revisions in order 1....6, then in order 6....1,
  then in arbitrary (staggered) order.  (A 'clean' is performed as part of
  each checkout, to ensure extraneous (non-member) resources are cleaned
  up.

There are many internal integrity checks, validating t-core data structures
against both BranchImage datastructures and the Eclipse resource hierarchy.
These turned up a number of bugs along the way (mostly in my code; several
early ones in 'inherited' code), so I'm fairly confident the tests are working as 
expected (at least, for everything I've thought to test for, so far!).

At this point, core checkin, checkout and add/remove/move resource operations
seem pretty solid. Next steps include:

* re-enabling and updating the ResourceChangeTracker code, so that the
  t-client updates the working image automatically in response to Eclipse
  resource change operations
* revising the existing test suite to verify the RC Tracker is working as expected (At present, the tests explicitly update the working image as Eclipse resources change)
* Resuscitating the previous GUI client code, to get basic functionality working with the new t-core * Adding basic (non-visual) merge capabilities (i.e. like current CLI merges).
After that, I'll probably start working on some spiffy visual sync/merge viewer support ... unless the newstore code is working at that point. In that case, I may switch immediately over to building a client for newstore. . It's worth noting that adding visual sync to the current Stellation core will require some API changes to the core; if we're ready to migrate to newstore, changing the old API 
would not be worthwhile.

- 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