Re: [VOTE] Promote iBATIS 2.3.2 to General Availability -- Java 5 Required...
+1 Jeff Butler On Thu, Jun 26, 2008 at 1:23 PM, Clinton Begin [EMAIL PROTECTED] wrote: This is a vote to promote iBATIS 2.3.2 to General Availability. One consequence of 2.3.2 is that it now requires Java 5. We've added support for Enums and therefore we cannot compile it under 1.4. It's possible to make a 1.4 compatible branch of the framework, but that can be a separate issue. If you've voting to promote this, then you're also voting to drop support for JDK 1.4 in the release. I like this approach, because it also prepares people for iBATIS 3.0...which will be Java 5 only. Clinton
Re: [VOTE] Promote iBATIS 2.3.2 to General Availability -- Java 5 Required...
+1 2008/6/26 Clinton Begin [EMAIL PROTECTED]: This is a vote to promote iBATIS 2.3.2 to General Availability. One consequence of 2.3.2 is that it now requires Java 5. We've added support for Enums and therefore we cannot compile it under 1.4. It's possible to make a 1.4 compatible branch of the framework, but that can be a separate issue. If you've voting to promote this, then you're also voting to drop support for JDK 1.4 in the release. I like this approach, because it also prepares people for iBATIS 3.0...which will be Java 5 only. Clinton
Re: [VOTE] Promote iBATIS 2.3.2 to General Availability -- Java 5 Required...
+1 As a side note there are tools that can backport java 5 code to java 1.4. Tools like Retrotranslator (http://retrotranslator.sourceforge.net/). Brandon Goodin On Thu, Jun 26, 2008 at 1:23 PM, Clinton Begin [EMAIL PROTECTED] wrote: This is a vote to promote iBATIS 2.3.2 to General Availability. One consequence of 2.3.2 is that it now requires Java 5. We've added support for Enums and therefore we cannot compile it under 1.4. It's possible to make a 1.4 compatible branch of the framework, but that can be a separate issue. If you've voting to promote this, then you're also voting to drop support for JDK 1.4 in the release. I like this approach, because it also prepares people for iBATIS 3.0...which will be Java 5 only. Clinton
Re: [VOTE] Promote iBATIS 2.3.2 to General Availability -- Java 5 Required...
+1, welcome to the 21st century. ;-) Larry On Fri, Jun 27, 2008 at 7:52 PM, Brandon Goodin [EMAIL PROTECTED] wrote: +1 As a side note there are tools that can backport java 5 code to java 1.4. Tools like Retrotranslator (http://retrotranslator.sourceforge.net/). Brandon Goodin On Thu, Jun 26, 2008 at 1:23 PM, Clinton Begin [EMAIL PROTECTED] wrote: This is a vote to promote iBATIS 2.3.2 to General Availability. One consequence of 2.3.2 is that it now requires Java 5. We've added support for Enums and therefore we cannot compile it under 1.4. It's possible to make a 1.4 compatible branch of the framework, but that can be a separate issue. If you've voting to promote this, then you're also voting to drop support for JDK 1.4 in the release. I like this approach, because it also prepares people for iBATIS 3.0...which will be Java 5 only. Clinton
[VOTE] Promote iBATIS 2.3.2 to General Availability -- Java 5 Required...
This is a vote to promote iBATIS 2.3.2 to General Availability. One consequence of 2.3.2 is that it now requires Java 5. We've added support for Enums and therefore we cannot compile it under 1.4. It's possible to make a 1.4 compatible branch of the framework, but that can be a separate issue. If you've voting to promote this, then you're also voting to drop support for JDK 1.4 in the release. I like this approach, because it also prepares people for iBATIS 3.0...which will be Java 5 only. Clinton
