[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[stellation-res] Patch posted: Enhanced error reporting for Eclipse client.
|
I have just entered Bugzilla #32535
"Repository access and other Core errors are often not reported to the user"
The current Eclipse client has very weak error reporting. The existing code
was designed to report errors via log4j, and should be modified to report
errors to the user via standard Eclipse mechanisms.
The posted zip contains two patches.
(1) The scm.model patch modifies scm.model internal error reporting to route
most error reports to the standard plugin log for the scm.model plugin.
The revised code is probably reporting too many errors to the end user, and
we should probably prune the set of user-visible error messages, routing
excluded error messages to an internal debug log.
(2) The scm.ui patch adds a new class, ModelStatusReporter, which listens for
log entries made to the scm.model log. These are reported to the user via a
standard popup dialog. Additional patch elements include some fixes to the
previous error popup dialog, and insertion of a ModelStatusReporter into
various repository-related operations (project creation/sharing, the
InfoLister, checkin/checkout, etc.).
Note: the scm.model patch also includes code to disable a particular
AccessSpec
for the remainder of the Eclipse session if the repository connection
cannot be established.
The intent is to prevent repeated cascades of error messages (which occured
during my
earlier testing). On further thought, this seems a bit draconian, and I
propose to
modify AccessSpec management so that the AccessSpec dialog both displays the
disabled status and allows the user to re-enable a given AccessSpec after
correcting
the repository connection problem (e.g. by starting up the server that one
neglected
to start before running Eclipse ....).
If someone can test this patch soon, great!
If nobody gets to it before I update the scm.model code to support
re-enabling disabled
AccessSpecs, I'll just replace the currently-posted patch and then request
a patch check again.
- 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
