Conor writes:

| [EMAIL PROTECTED] wrote:

| > Yep,
| > 
| > Gump help alerts the developers to the issue.
| > 
| > But, how many people will use JDOM? It'd be better if API breakages 
were 
| > reported as a group, rather than each group needing to 
| > discover/report/troubleshoot them.
| > 
| > And it would be nice if Gump could, on request, report the breakage to 
the 
| > component being used, rather than a developer needing to sign up on 
the 
| > mailing lists. 
| 
| 
| Do you mean reproting the error to the dependency which introduce the 
problem? I 
Not automatically, on request.

| wonder how feasible it would be and how many false positives it would 
generate. 
Hopefully, as many as it currently does via the wetware method :)
| Determining the root cause of a breakage is probably going to remain a 
wetware 
| task at the point the breakage manifests itself.
And I'm not advocating changing that....

| How would you determine to which dependency a failure is to be 
attributed, if 
| indeed it is not a bug in the project itself? The recent Latka DTD 
problem could 
| have had a number of causes
| 1. A change in Xerces making the DTD appear bad
| 2. A change in Ant causing the style task to encounter some fatal 
exception
| 3. A change in the DTD itself
| 4. A change in the external Gump environment (OS, network, etc).
| 
| It usually requires detailed analysis to uncover the root cause.
At which point, if gump had an 'report bug' url template associated with 
the project, a developer could request a gump bug report gets sent to the 
offending project. It means I personally don't have to go see if they're 
using Bugzilla or Scarab or Stomp or whatever as they're bug tracking 
system, and file a report with the gump run details. All the info is help 
by gump.

It's a 'service' gump could provide by tracking/adding bug submission 
details to the project definition.

--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to