headers
Mark Rotteveel | 7 Apr 2012 22:23
Picon

Beta version of Jaybird 2.2 released

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.0 
beta-1.

This release contains the following changes:
* Enhanced support for JDBC 4.0 (Java 6)
* Support for JDBC 4.1 (Java 7) - including try-with-resources support,
* Implementation of getGeneratedKeys(),
* Enhanced support for the services API,
* Support for 64 bit native libraries for Type 2 / Embedded,
* A number of bug fixes

The beta release is also available on maven(*):
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.0-beta-1</version>

The artifactId depends on your target Java version: jaybird-jdk15, 
jaybird-jdk16 or jaybird-jdk17

Problems, bugs: please mail us on the Firebird-Java group or add a 
ticket to the tracker on http://tracker.firebirdsql.org/browse/JDBC

*) As this is the first release to Maven and we need manual 
authorization from Sonatype, it can take several days before the 
artifacts are really available on Maven
--

-- 
Mark Rotteveel

------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Rotteveel | 7 Apr 2012 22:24
Picon

Beta version of Jaybird 2.2 released (now with link)

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.0 
beta-1.

This release contains the following changes:
* Enhanced support for JDBC 4.0 (Java 6)
* Support for JDBC 4.1 (Java 7) - including try-with-resources support,
* Implementation of getGeneratedKeys(),
* Enhanced support for the services API,
* Support for 64 bit native libraries for Type 2 / Embedded,
* A number of bug fixes

Downloads are available from:
https://sourceforge.net/projects/firebird/files/firebird-jca-jdbc-driver/

The beta release is also available on maven(*):
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.0-beta-1</version>

The artifactId depends on your target Java version: jaybird-jdk15, 
jaybird-jdk16 or jaybird-jdk17

Problems, bugs: please mail us on the Firebird-Java group or add a 
ticket to the tracker on http://tracker.firebirdsql.org/browse/JDBC

*) As this is the first release to Maven and we need manual 
authorization from Sonatype, it can take several days before the 
artifacts are really available on Maven
--

-- 
Mark Rotteveel
(Continue reading)

Permalink | Reply | 0 comments |
headers
nspickles | 22 Apr 2012 15:51
Picon

Differences between FB v2.0.x & FB v2.1.x

This may be a daft question but I have spent a good while looking around the Firebird website and I can't find
an answer.

What are the major differences between FB v2.0.x and FB v2.1.5 ? Why would someone go for v2.0.x over v2.1.x
or vice-versa ?

I ask this because while we are currently using v2.1.4, I noted that a new version, v2.0.7, was recently
released and was kind of wondering why v2.0.x was still being developed when v2.1.x seemed so similar to it.

------------------------------------
Permalink | Reply | 1 comment |
headers
Helen Borrie | 22 Apr 2012 21:18
Picon
Favicon

Re: Differences between FB v2.0.x & FB v2.1.x

At 01:51 AM 23/04/2012, nspickles wrote:
>This may be a daft question but I have spent a good while looking around the Firebird website and I can't find
an answer.

Release notes!

http://www.firebirdsql.org/file/documentation/release_notes/html/rlsnotes207.html

http://www.firebirdsql.org/file/documentation/release_notes/html/rlsnotes210.html

Note that the changes in 2.0.1 are folded into the 2.1 release notes, in general.  The first two chapters in
each case give you the summaries and the links to the detail.

>What are the major differences between FB v2.0.x and FB v2.1.5 ? Why would someone go for v2.0.x over v2.1.x
or vice-versa ?
>
>I ask this because while we are currently using v2.1.4, I noted that a new version, v2.0.7, was recently
released and was kind of wondering why v2.0.x was still being developed when v2.1.x seemed so similar to it.

As always, a new major release steps onward from the previous one and maintenance sub-releases have bug
fixes and improvements but no new features.  We continue doing maintenance sub-releases for each major
release for some years. In fact, v.2.1.5 is in QA right now, even as we prepare for 2.5.2 and the 3.0 alpha.

There'd be no reason to go to 2.0.x now.  V.2.0.7 is probably the last sub-release of the 2.0 series.  It could
be similarly argued that there'd be no strong reason to move from 1.5 to 2.1, given that the current major
release, 2.5.x, is into its third round of bug fixes.  We're not likely to see more than one or two
sub-releases of the 2.1 series beyond 2.1.5

Helen
(Continue reading)

Permalink | Reply | 0 comments |

Gmane