2019-09-30 22:48 UTC+02:00, Alex Herbert :
> The JMH examples project contains an increasing number of benchmarks. I
> suggest a simple refactor to packages that follow the package names of the
> four components to which the benchmarks apply.
>
> Currently there is:
>
>
The JMH examples project contains an increasing number of benchmarks. I suggest
a simple refactor to packages that follow the package names of the four
components to which the benchmarks apply.
Currently there is:
org.apache.commons.rng.examples.jmh
Hi Mark,
I know you said you fixed a bunch of warnings but I still warning get these
using CPU=X64; I had only tested CPU=X86 previously (sorry):
C:\Program Files (x86)\Windows
Kits\10\include\10.0.17763.0\ucrt\corecrt_wstring.h(139): warning C4391:
'size_t wcslen(const wchar_t *)': incorrect
Couldn't resist
https://twitter.com/alanparsons/status/1178469148751466496?s=19
...no idea how it appeared in my timeline...
- - -
Vice President Marketing & Publicity
Vice President Sponsor Relations
The Apache Software Foundation
Tel +1 617 921 8656 | s...@apache.org
On Thu, Sep 19,
A further regression has been identified in the 1.2.0/1.2.1 releases so
I'd like to get 1.2.2 released to address it. So, time for another
release vote.
Notable changes since 1.2.1 include:
- Correct a regression (DAEMON-408) that caused Windows services to
crash on start-up when the universal
On Mon, Sep 30, 2019 at 9:26 AM Mark Thomas wrote:
> I am cancelling this vote due to the presence of Windows build artefacts
> in RC1.
>
> RC2 should follow shortly.
>
>
Mark,
Thank you for working through all of this. I know this will make for a
better product :-)
Gary
> Mark
>
>
>
I am cancelling this vote due to the presence of Windows build artefacts
in RC1.
RC2 should follow shortly.
Mark
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
On 2019-09-30, sebb wrote:
> On Mon, 30 Sep 2019 at 10:25, Stefan Bodewig wrote:
>> On 2019-09-29, sebb wrote:
>>> On Sun, 29 Sep 2019 at 17:21, Matt Sicker wrote:
Projects that have a configure script usually include that in the source
distribution but not in the source repository
May we get more PMC reviews please?
Gary
On Thu, Sep 26, 2019 at 9:38 PM Gary Gregory wrote:
> We have fixed one important bug since Apache Commons BCEL 6.4.0 was
> released, so I would like to release Apache Commons BCEL 6.4.1.
>
> Apache Commons BCEL 6.4.1 RC1 is available for review here:
>
On 28/09/2019 17:42, Mark Thomas wrote:
> On 28/09/2019 17:06, Gary Gregory wrote:
>> On Sat, Sep 28, 2019 at 12:04 PM Gary Gregory
>> wrote:
>>> I can build without errors but with warnings:
>>>
>>> .\..\..\apps\prunsrv\prunsrv.c(323): warning C4996: '_wfopen': This
>>> function or variable
On Mon, 30 Sep 2019 at 10:25, Stefan Bodewig wrote:
>
> On 2019-09-29, sebb wrote:
>
> > On Sun, 29 Sep 2019 at 17:21, Matt Sicker wrote:
>
> >> Projects that have a configure script usually include that in the source
> >> distribution but not in the source repository (at least for autotools
>
On 2019-09-29, sebb wrote:
> On Sun, 29 Sep 2019 at 17:21, Matt Sicker wrote:
>> Projects that have a configure script usually include that in the source
>> distribution but not in the source repository (at least for autotools
>> users).
> But is that correct?
This is what people expect.
As
On Mon, 30 Sep 2019 at 09:23, Mark Thomas wrote:
>
> On 29/09/2019 23:15, Gary Gregory wrote:
> > On Sun, Sep 29, 2019 at 6:04 PM sebb wrote:
> >
> >> On Sun, 29 Sep 2019 at 22:36, Matt Sicker wrote:
> >>>
> >>> I’m sort of going off of what GNU projects do (they use autotools for
> >> any C
>
On 29/09/2019 23:15, Gary Gregory wrote:
> On Sun, Sep 29, 2019 at 6:04 PM sebb wrote:
>
>> On Sun, 29 Sep 2019 at 22:36, Matt Sicker wrote:
>>>
>>> I’m sort of going off of what GNU projects do (they use autotools for
>> any C
>>> projects), but the common ‘./configure && make && sudo make
14 matches
Mail list logo