To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-xmlunit contains errors.
The current state of this
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
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jaxme contains errors.
The current state of this
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-fmt-test has an issue affecting its community
+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
+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
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
This release includes support for Java5 generics and varargs.
In RC3 I accidentally added a dependency on Java 1.6 while fixing FindBugs
errors; in RC4 I fixed that bug.
As noted in earlier RCs, I believe 1.3 to be a backwards compatible binary, but
I'm still only 99% sure of this; clirr
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 :
+1
Dan Fabulich wrote:
This release includes support for Java5 generics and varargs.
In RC3 I accidentally added a dependency on Java 1.6 while fixing FindBugs
errors; in RC4 I fixed that bug.
As noted in earlier RCs, I believe 1.3 to be a backwards compatible
binary, but I'm still
Dan Fabulich a écrit :
This release includes support for Java5 generics and varargs.
In RC3 I accidentally added a dependency on Java 1.6 while fixing
FindBugs errors; in RC4 I fixed that bug.
There is a new (very minor) checkstyle error in this version. This is
not blocking.
+1
Luc
+1
Oliver
Dan Fabulich schrieb:
This release includes support for Java5 generics and varargs.
In RC3 I accidentally added a dependency on Java 1.6 while fixing
FindBugs errors; in RC4 I fixed that bug.
As noted in earlier RCs, I believe 1.3 to be a backwards compatible
binary, but I'm
+1
Julien
2009/11/8 Dan Fabulich d...@fabulich.com:
This release includes support for Java5 generics and varargs.
In RC3 I accidentally added a dependency on Java 1.6 while fixing FindBugs
errors; in RC4 I fixed that bug.
As noted in earlier RCs, I believe 1.3 to be a backwards compatible
Hi!
looking at Ralph's comment in
https://issues.apache.org/jira/browse/VFS-254
I am questionning myself, if there's any reason why vfs 2.0 should
still
have JDK 1.4 as requirement and not JDK 1.5.
If it is just me, I'd be happy to drop 1.4 dependency - Past votes were
declined. Probably
-Original Message-
From: news [mailto:n...@ger.gmane.org] On Behalf Of Jörg Schaible
Sent: Sunday, November 08, 2009 22:24
To: dev@commons.apache.org
Subject: [vfs] JDK 1.5
Guys,
looking at Ralph's comment in
https://issues.apache.org/jira/browse/VFS-254
I am questionning
On Nov 8, 2009, at 10:24 PM, Jörg Schaible wrote:
Guys,
looking at Ralph's comment in https://issues.apache.org/jira/browse/VFS-254
I am questionning myself, if there's any reason why vfs 2.0 should
still
have JDK 1.4 as requirement and not JDK 1.5. VFS 2.0 will be a major
release and JDK
17 matches
Mail list logo