We have fixed a few bugs and added enhancements since Apache Commons
Codec 1.16.1 was released, so I would like to release Apache Commons
Codec 1.17.0.
Apache Commons Codec 1.17.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1
(svn revision
So that's +1 (sorry for the misfired email).
The Java 21 I tested is:
openjdk version "21.0.2" 2024-01-16
OpenJDK Runtime Environment Homebrew (build 21.0.2)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
Gary
On Sat, Apr 20, 2024 at 1:40 PM Gary Gregory wrote:
>
>
Tested src zip file:
- SHA512 OK
- ASC OK
- `mvn` (default goal) OK
Using Java 17 OK:
openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
Apache Maven 3.9.6
Hi Gary,
> Am 20.04.2024 um 15:30 schrieb Gary D. Gregory :
>
> Something is wrong with at least one ASC file:
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/commons-jcs3-dist-3.2.1-src.zip.asc
>
> $ gpg --verify commons-jcs3-dist-3.2.1-src.zip.asc
> gpg: assuming signed data
I don't what would go in this new component though. The tests in the
components I looked at don't have anything to share AFAICT.
Gary
On Sat, Apr 20, 2024, 12:13 PM Gilles Sadowski wrote:
> Hi.
>
> Le sam. 20 avr. 2024 à 17:50, Gary Gregory a
> écrit :
> >
> > Hello,
> >
> > I looked at
Hi.
Le sam. 20 avr. 2024 à 17:50, Gary Gregory a écrit :
>
> Hello,
>
> I looked at Commons Lang, Commons IO, Commons CSV, Commons BCEL, Commons
> Crypto, and Commons Text. All of the above do the same duplicate work.
For sure, it's an improvement to make duplicate configurations obsolete.
Hello,
I looked at Commons Lang, Commons IO, Commons CSV, Commons BCEL, Commons
Crypto, and Commons Text. All of the above do the same duplicate work.
Gary
On Sat, Apr 20, 2024, 11:01 AM Gilles Sadowski wrote:
> Hi.
>
> This commit caught my attention but I've not looked in detail (sorry!).
>
Hi.
This commit caught my attention but I've not looked in detail (sorry!).
I'm wondering whether this addition deserves a discussion here on "dev"
to reach consensus on how to handle benchmarking code in a uniform
way across all components.
For a long time, some components (namely and mainly
Something is wrong with at least one ASC file:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2/commons-jcs3-dist-3.2.1-src.zip.asc
$ gpg --verify commons-jcs3-dist-3.2.1-src.zip.asc
gpg: assuming signed data in 'commons-jcs3-dist-3.2.1-src.zip'
gpg: Signature made Sat, Apr 20, 2024
On Sat, 20 Apr 2024 at 11:36, Claude Warren wrote:
> The LayerdBloomFilter has a method find() that returns an array of ints
> that are the indices into the layer array. This is easily reproducible
> using an iterator.
> There is also get() method that takes an integer argument (an index of
The LayerdBloomFilter has a method find() that returns an array of ints
that are the indices into the layer array. This is easily reproducible
using an iterator.
There is also get() method that takes an integer argument (an index of the
bloom filter) and returns the Bloom filter from the layer.
My vote.
> Am 20.04.2024 um 12:25 schrieb Thomas Vandahl :
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I
> would like to release Apache Commons JCS 3.2.1.
>
> Apache Commons JCS 3.2.1 rc2 is available for review here:
>
Hi folks,
We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I would
like to release Apache Commons JCS 3.2.1.
Apache Commons JCS 3.2.1 rc2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc2 (svn revision
68673)
The Git tag
13 matches
Mail list logo
