I'd like to know how much of 2.x is deprecated. We may need 3.x to be JDK1.3 compatible but without the deprecations. And thus 4.x () to be JDK1.5.
Anyway, for me, the project and version number should depend on compatibility. We shouldn't release any new version, even of a major version number, that isn't fully binary compatible. The only thing we can do is remove deprecated methods. (Adding generics can be binary compatible) Stephen ----- Original Message ---- From: Henri Yandell <[EMAIL PROTECTED]> To: Jakarta Commons Developers List <[email protected]> Sent: Thursday, 15 February, 2007 8:46:38 AM Subject: [lang] 3.0 thoughts again So... I'd like to: * Move to JDK 1.5 as a minimum (generating class 49 jars to stop accidental usage on pre 1.5). * Remove deprecated code. * Look into other code to deprecate based on the move to JDK 1.5. * Create a CI site, as opposed to a user site. * Move to an m2 build (dropping ant/m1). Based on previous discussions, I'm presuming some of this will raise opinions. Does anyone mind if I start playing with the above on an experimental -3.0 branch (trunk would become 2.4-SNAPSHOT)? Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
