> >> [...] > > > > It seems the thread asking for help on the exception API design is going > > to be fruitful, and it starts well with interesting ideas. I guess some > > of these ideas will change again our view and we will converge > > (hopefully not throwing an exception ourselves ...) to a stable design > > for 3.0. It seems to me that the switch to unchecked exceptions is > > supported by almost all participants to this thread, so this part is > > probably already stabilized. > > > > I doubt we can do anything about it for 2.2 and waiting first for the > > rest of the discussion to stabilize (no hierarchy/small hierarchy/large > > hierarchy, specific getters/general context map ...) would push 2.2 too far. > > > > I would like to freeze 2.2 as it is now in the repository and get it out. > > > > What do you think ? > > > > +1 for getting the release out. Given that we are not sure how things > are going to end up in 3.0, we should remove the deprecations.
Which things? Which deprecations? Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
