On 9/20/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > - the jar is getting a little porky, at nearly 250K.
>
> 3.0 and removing deprecations might help a little there.
Should we plan on delivering whatever we delete, like the enum package,
in a separate jar for backwards binary compatibility?
Nope, life moves on. If we get some world shattering bug, we can
release 2.2.1, or 2.3.1 or something. Just as we would do 1.0.2 today
if there was need for a bugfix and lots of people couldn't move to
2.x.
A separate binary jar is just make-work I think, until we hit a time
when someone needs it. Better spent on dbcp, or cli, or ... :)
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
