I plan to do the following (if there are no objections) before trying to do a Commons Chain release:
1) Fix remaining Checkstyle issues (I've made a start on this) note: DispatchCommand has 3 protected variables (methods, method and methodKey) which I plan to make private (method and methodKey have read/write methods) since it hasn't yet been in a release. There are quite a few protected instance variables in other (released) Chain classes. We could deprecate them all in this release, so that they could be made private in a later version. I don't have a strong opinion, but would probably be a good idea - if theres a consensus to do this I don't mind doing the work. 2) Fix CHAIN-29 Remove static Log instances http://issues.apache.org/jira/browse/CHAIN-29 3) Implement CHAIN-28 [2] - Provide a Map of Cookies in WebContext Interface http://issues.apache.org/jira/browse/CHAIN-28 I'm off on holiday for a week, so I probably won't be responding to comments on this (or doing any of the above) until after that. Niall On 5/24/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
I've made a few changes to Commons Chain, which except for one minor bug were all related to the site/docs and maven build. Looking through the open bugs, there seems to be only one actual bug (maybe two) outstanding: http://issues.apache.org/jira/browse/CHAIN-4 (maybe http://issues.apache.org/jira/browse/CHAIN-12) I've created some release notes showing the changes since Chain 1.0: http://jakarta.apache.org/commons/chain/changes-report.html If there are no objections I'd like to create a 1.1 release candidate - leaving CHAIN-4 for later. Niall
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
