Hello.
2019-09-20 18:45 UTC+02:00, Alex Herbert :
> I have added some new sections to the user guide for new additions to
> the library.
>
> Currently the section on JumpableUniformRandomProvider gives an example:
>
> RandomSource source = RandomSource.XO_RO_SHI_RO_128_SS; // Known to be
>
We have fixed quite a few bugs and added some enhancements since Apache
Commons BCEL 6.3.1 was released, so I would like to release Apache Commons
BCEL 6.4.0.
Apache Commons BCEL 6.4.0 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.0-RC2 (svn
I have added some new sections to the user guide for new additions to
the library.
Currently the section on JumpableUniformRandomProvider gives an example:
RandomSource source = RandomSource.XO_RO_SHI_RO_128_SS; // Known to be jumpable.
JumpableUniformRandomProvider master =
So is it safe to add a rel/ tag for the same commit as 2.6 RC3? Will you do
that or shall I?
Gary
On Fri, Sep 20, 2019 at 8:37 AM sebb wrote:
> On Fri, 20 Sep 2019 at 13:30, Gary Gregory wrote:
> >
> > Based on the "I’ll publish the release tomorrow." below it looks like he
> > did publish it
On Fri, 20 Sep 2019 at 13:30, Gary Gregory wrote:
>
> Based on the "I’ll publish the release tomorrow." below it looks like he
> did publish it since it is in the maven repo, on dist, and the site is up,
> but seems to have not completed all the steps.
> I could not find an announce email for 2.5
Based on the "I’ll publish the release tomorrow." below it looks like he
did publish it since it is in the maven repo, on dist, and the site is up,
but seems to have not completed all the steps.
I could not find an announce email for 2.5 either, could you?
Gary
On Fri, Sep 20, 2019 at 7:38 AM
It looks like this was not completed: could not find an announce
email, and the tag has not been created (see recent user@ email)
On Wed, 18 Oct 2017 at 19:26, Benedikt Ritter wrote:
>
> Hello,
>
> > Am 15.10.2017 um 12:22 schrieb Benedikt Ritter :
> >
> > Hello,
> >
> > we have fixed quite a
If you are looking for tests for interfaces take a look at contract testing
(https://github.com/Claudenw/junit-contracts)
On Fri, Sep 20, 2019 at 9:40 AM Rohan Suri wrote:
> Apologies I wasn't aware the test jars are being released as well.
> Adding "classifier: tests" when specifying the
Hi,
The Abstract* tests for collections seem pretty useful to be in a separate
jar so that they could be reused by anyone wanting to test a new map
implementation.
If the idea seems fine, I'd be happy to take up the task and discuss the
required changes in pom, etc.
Rohan.
Apologies I wasn't aware the test jars are being released as well.
Adding "classifier: tests" when specifying the dependency does the job.
On Fri, Sep 20, 2019 at 1:05 AM Rohan Suri wrote:
> Hi,
>
> The Abstract* tests for collections seem pretty useful to be in a separate
> jar so that they
10 matches
Mail list logo