On Sun, Mar 8, 2009 at 10:45 PM, Dan Fabulich wrote:
> "NEEDS" is a little strong I think there's room in the world for a
> backwards-compatible dbutils 1.3 with generics and varargs followed shortly
> afterward by a more thoroughly re-worked dbutils 2.0.
That sounds like a good approach. D
On 08/03/2009, Dan Fabulich wrote:
>
> My first attempt at releasing a commons project; please be gentle. :-)
>
> Compatibility warning: This version is mostly a bugfix release, but to fix
> DBUTILS-31 we had to upgrade the JVM dependency from JDK 1.3 to JDK 1.4.
> Except for that, it is backwar
Liam Coughlin wrote:
the code NEEDS to change though, and not in a backwards compatible way. Do
whatever is appropriate with version numbers to indicate that non-binary
compatible changes are coming.
"NEEDS" is a little strong I think there's room in the world for a
backwards-compatible
On 09/03/2009, Dan Fabulich wrote:
>
> Who is on the Apache Commons Project Management Committee? (Google has
> failed me.)
>
> I see this http://commons.apache.org/charter.html but I
> assume that list is out of date...?
Yes, it was correct as the initial list, but of course that has
changed
Who is on the Apache Commons Project Management Committee? (Google has
failed me.)
I see this http://commons.apache.org/charter.html but I assume that list
is out of date...?
-Dan
-
To unsubscribe, e-mail: dev-unsubscr...
Hi folks,
OK then, so don't be surprised if I start to commit. I will have to make me
familiar with the experimental branch first though.
Oliver Heger wrote:
> I am fine with both points and also agree with the comments of Ralph.
>
> 1) sounds that the current implementation is buggy - or at le
Hi Dan,
I've downloaded the src tar ball and tried to build the version with my
compiler zoo. It runs fine with all Sun JDKs, IcedTea6, Blackdown 1.4.2,
JRockit 1.4 and 1.5. As usual the build faisl for IBM JDK 1.4 and 1.5
because Maven fails itself on this versions. However, IBM JDK 6 fails here:
the code NEEDS to change though, and not in a backwards compatible way. Do
whatever is appropriate with version numbers to indicate that non-binary
compatible changes are coming.
Cheers,
-L
On Sun, Mar 8, 2009 at 6:04 AM, Stephen Colebourne <
scolebou...@btopenworld.com> wrote:
> Dan Fabulich w
I found http://issues.apache.org/struts/browse/WW-2736 in a particular
scenario.
I think the problem is not having any relation with the browser.
TokenSessionStoreInterceptor.java
has two methods:
protected
String
handleInvalidToken
(
ActionInvocation
invocation)
throws
Exception
();
protected
Dan Fabulich wrote:
Henri Yandell wrote:
The Java5 version is more up for debate. If the API is no longer
compatible, then we start to lean to 2.0. Especially as calling it 2.0
allows for more of an overhaul of API.
The the API in the "java5" branch is backward compatible; the generics
and v
My first attempt at releasing a commons project; please be gentle. :-)
Compatibility warning: This version is mostly a bugfix release, but to fix
DBUTILS-31 we had to upgrade the JVM dependency from JDK 1.3 to JDK 1.4.
Except for that, it is backwards compatible with DbUtils 1.1.
PLEASE TEST
11 matches
Mail list logo
