Today I tried to find where a bug reported against what I suspect is
DBCP 1.4 (I think that is likely what tomcat 7 pulls in) was fixed. It
appears to be fixed in the 1.5 branch, but it is impossible now to
actually see history via the browser. The git browser has a "history"
link, but
Hello.
Le lun. 7 oct. 2019 à 19:42, Claude Warren a écrit :
>
> As noted earlier I am preparing a contribution of Bloom Filter classes to
> the collections module. As part of this submission there are several
> methods that operate on BitSets that are used as part of Bloom Filter
>
Hi.
Le lun. 7 oct. 2019 à 19:01, Claude Warren a écrit :
>
> Greetings,
>
> I am preparing a pull request to bring Bloom Filters in the the
> collections package. The pull requests is at
> https://github.com/apache/commons-collections/pull/83 and the Jira ticket
> is
On Thu, 10 Oct 2019 at 08:53, John Patrick wrote:
>
> what about people wanting to use it on java 12 or java 13.
Please explain what you mean.
Are you saying that code compiled with Java 5 will not run on Java 12+ ?
Is not, why not?
> if java 1.5 and not wanting to upgrade is the argument, why
what about people wanting to use it on java 12 or java 13.
if java 1.5 and not wanting to upgrade is the argument, why would they be
upgrading the software...
if a company is choosing to use and run an out of support jvm’s then it is a
risk they are choosing to accept, either implicity or
The problem sometimes not are the developers and their desire of upgrading. The
problem are the clients that don't desire to upgrade the JVM that have
installed in their servers.
I had a case where a client was running a Sun Java 5 JVM with a bug on String
class that sometimes calculated bad
+1 for java 8
I just assume developers who still using java 6 do not care about
upgrading their commons too...
But what is the meaning of jigsawI mean, everybody use maven and
maven is good, right?
sebb 于2019年10月10日周四 上午6:55写道：
>
> On Wed, 9 Oct 2019 at 22:38, John Patrick wrote:
> >
> >
