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. On the community aspect of things, If Latka is broken for example, all the dependencies *may* be interested, as they all have a vested interested in client code continuing to work, especially if it was within Jakarta. In the last month, Latka has been 'broken' twice now by external libraries, Xerces & JDOM. I'd have thought, given how many projects are built by Gump, others would've hit the same issues. Looks like we need more gump users. On the JDOM issue, it was a decision they chose to make. I'm not convinced changing a public API without first deprecating it, even to add an exception, is a good thing. The work around code to support both is ugly. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers "Sam Ruby" <[EMAIL PROTECTED]> 05/05/02 04:09 PM Please respond to "Alexandria Developers List" To: "Alexandria Developers List" <[EMAIL PROTECTED]> cc: Subject: Re: Found it dIon Gillard wrote: > > Is there a gump standard way of reporting API breaking? I've found the > JDOM API has changed in the cvs code for b7 and b8 :( Not that I'm aware of. > I'd rather not have to personally join every single mailing list related > to java. That's actually the point. Instead of continuously monitoring every project that you might depend on, or waiting until it is may very well be too late, Gump can given you an indication as to when *MIGHT* be a good idea to get involved. I have found Jason Hunter <[EMAIL PROTECTED]> to be very responsive to any JDOM issues that are brought to his attention. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
