+1 - drop it. I'd rather put the effort into the Javadoc. That is where my focus was when working on the updates for pool 2.0.
I'd add that one of the things that drove me mad with pool 2 was that the same information was repeated in multiple places and trying to keep them in sync is really hard work. I'm a big fan of write once, reference everywhere. For me the Javadoc should be the primary source of information. Mark Gary Gregory <garydgreg...@gmail.com> wrote: >Drop it! > >Gary > >On Tue, Jun 26, 2012 at 12:07 AM, Phil Steitz <phil.ste...@gmail.com> >wrote: > >> There is not much in this doc beyond class diagrams that are now out >> of date. Unless someone wants to volunteer to update the diagrams >> and maybe add some more meaningful content, I propose that we drop >> this for 2.0. We can always add it back later if someone gets >> inspired. Personally, I would see more value in a config guide, >> similar to what DBCP has. >> >> Any objections to dropping for 2.0, or volunteers to patch? >> >> Phil >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > >-- >E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 >Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK >Blog: http://garygregory.wordpress.com >Home: http://garygregory.com/ >Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
