Re: [VOTE] Release of DbUtils 1.3 RC3

2009-11-08 Thread Luc Maisonobe
Dan Fabulich a écrit : This release includes support for Java5 generics and varargs. For RC3 I fixed the CheckStyle and FindBugs errors, except for the bad practice bug of using getClass().getResourceAsStream(), which would probably require an API change. Thanks for taking care of these

Re: [VOTE] Release of DbUtils 1.3 RC3

2009-11-08 Thread Jörg Schaible
+1 again Dan Fabulich wrote: This release includes support for Java5 generics and varargs. For RC3 I fixed the CheckStyle and FindBugs errors, except for the bad practice bug of using getClass().getResourceAsStream(), which would probably require an API change. As noted in earlier

Re: [VOTE] Release of DbUtils 1.3 RC3

2009-11-08 Thread Julien Aymé
+1 as before. Thanks a lot for doing all this. Julien 2009/11/8 Dan Fabulich d...@fabulich.com: This release includes support for Java5 generics and varargs. For RC3 I fixed the CheckStyle and FindBugs errors, except for the bad practice bug of using getClass().getResourceAsStream(), which

Re: [VOTE] Release of DbUtils 1.3 RC3

2009-11-08 Thread Oliver Heger
I tried to build the sources on a JDK 1.5 and got the following errors: D:\data\projects\OpenSource\dbutils\commons-dbutils-1.3-src\src\java\org\apache\ commons\dbutils\wrappers\SqlNullCheckedResultSet.java:[216,53] cannot find symbol symbol : method copyOf(byte[],int) location: class

Re: [VOTE] Release of DbUtils 1.3 RC3

2009-11-08 Thread Dan Fabulich
D'oh! Good catch... Oliver Heger wrote: I tried to build the sources on a JDK 1.5 and got the following errors: D:\data\projects\OpenSource\dbutils\commons-dbutils-1.3-src\src\java\org\apache\ commons\dbutils\wrappers\SqlNullCheckedResultSet.java:[216,53] cannot find symbol symbol :

[VOTE] Release of DbUtils 1.3 RC3

2009-11-07 Thread Dan Fabulich
This release includes support for Java5 generics and varargs. For RC3 I fixed the CheckStyle and FindBugs errors, except for the bad practice bug of using getClass().getResourceAsStream(), which would probably require an API change. As noted in earlier RCs, I believe 1.3 to be a backwards