On Sun, 11 Feb 2018 00:46:23 +, sebb wrote:
On 11 February 2018 at 00:36, Gilles
wrote:
Hi.
Using CP 43, and JDK 9, the command
$ mvn test
fails, seemingly because of "animal-sniffer"[1].
Works fine for me.
Does it work in a project that contains "module-info.java"
files?
Indeed, ru
On 11 February 2018 at 00:36, Gilles wrote:
> Hi.
>
> Using CP 43, and JDK 9, the command
> $ mvn test
> fails, seemingly because of "animal-sniffer"[1].
Works fine for me.
> Indeed, running
> $ mvn -Danimal.sniffer.skip=true test
> lets the build proceed successfully.
>
> Gilles
>
> [1] Error
Hi.
Using CP 43, and JDK 9, the command
$ mvn test
fails, seemingly because of "animal-sniffer"[1].
Indeed, running
$ mvn -Danimal.sniffer.skip=true test
lets the build proceed successfully.
Gilles
[1] Error message is similar to the one reported here:
https://github.com/mojohaus/animal-
On Sat, Feb 10, 2018 at 12:44 PM, Gary Gregory
wrote:
> I created the ticket "[TEXT-113] Add an interpolator string lookup." and
> committed a working version with unit tests.
>
> Please note:
> - The code is in a new package o.a.c.t.lookup and I left the current
> code as intact as possible.
>
On Sat, 10 Feb 2018 20:50:26 +0100, Stefan Bodewig wrote:
On 2018-02-10, Gilles wrote:
On Sat, 10 Feb 2018 08:08:12 -0700, Gary Gregory wrote:
If a Java package and artifact ID contain "internal" or "private"
in
the
name, that would be pretty clear.
Do you suggest that, say, the benchmarki
On 2018-02-10, Gilles wrote:
> On Sat, 10 Feb 2018 08:08:12 -0700, Gary Gregory wrote:
>> If a Java package and artifact ID contain "internal" or "private" in
>> the
>> name, that would be pretty clear.
> Do you suggest that, say, the benchmarking codes in
> "commons-rng-jmh" should be located in
I created the ticket "[TEXT-113] Add an interpolator string lookup." and
committed a working version with unit tests.
Please note:
- The code is in a new package o.a.c.t.lookup and I left the current code
as intact as possible.
- The current StrLookup and StrMatcher are abstract classes and not
i
On Sat, Feb 10, 2018 at 8:28 AM, Oliver Heger
wrote:
>
>
> Am 10.02.2018 um 09:55 schrieb Stefan Bodewig:
> > On 2018-02-10, Simon Spero wrote:
> >
> >> Writing tests for osgi modules is painless... the second time :-P
> >
> > I said I "was pointed into a direction for writing a test ..." that's
On Sat, 10 Feb 2018 08:08:12 -0700, Gary Gregory wrote:
If a Java package and artifact ID contain "internal" or "private" in
the
name, that would be pretty clear.
Do you suggest that, say, the benchmarking codes in
"commons-rng-jmh" should be located in a top package
named "o.a.c.rng.jmh.inter
On Sat, 10 Feb 2018 16:12:55 +, sebb wrote:
On 10 February 2018 at 14:20, Gilles
wrote:
On Sat, 10 Feb 2018 13:39:49 +, sebb wrote:
On 10 February 2018 at 12:57, Gilles
wrote:
On Sat, 10 Feb 2018 11:52:24 +, sebb wrote:
The 3rd party mirrors all offer their services for fre
On 10 February 2018 at 14:20, Gilles wrote:
> On Sat, 10 Feb 2018 13:39:49 +, sebb wrote:
>>
>> On 10 February 2018 at 12:57, Gilles wrote:
>>>
>>> On Sat, 10 Feb 2018 11:52:24 +, sebb wrote:
The 3rd party mirrors all offer their services for free.
Although storag
Am 10.02.2018 um 09:55 schrieb Stefan Bodewig:
> On 2018-02-10, Simon Spero wrote:
>
>> Writing tests for osgi modules is painless... the second time :-P
>
> I said I "was pointed into a direction for writing a test ..." that's
> been your and Bertrand's input. :-)
>
>> The key to making tests
If a Java package and artifact ID contain "internal" or "private" in the
name, that would be pretty clear.
Gary
On Feb 10, 2018 07:17, "Stefan Bodewig" wrote:
> On 2018-02-10, Gilles wrote:
>
> > Is there a convention for distinguishing codes with
> > compatibility requirements from codes provi
You can also look at the log4j-osgi module.
It does. It does some load testing for log4j's own budles.
Gary
On Feb 9, 2018 21:21, "Simon Spero" wrote:
> Writing tests for osgi modules is painless... the second time :-P
>
> The key to making tests easy is to use pax-exam, which handles most of th
On Sat, 10 Feb 2018 13:39:49 +, sebb wrote:
On 10 February 2018 at 12:57, Gilles
wrote:
On Sat, 10 Feb 2018 11:52:24 +, sebb wrote:
The 3rd party mirrors all offer their services for free.
Although storage is cheap these days, it is not free, so we should
not
burden the mirrors wit
On 2018-02-10, Gilles wrote:
> Is there a convention for distinguishing codes with
> compatibility requirements from codes provided as
> development tools (unit tests, benchmarking, usage
> examples, integration tests, ...)?
In Compress we once had a package named _internal_ and a package level
j
Hello.
Is there a convention for distinguishing codes with
compatibility requirements from codes provided as
development tools (unit tests, benchmarking, usage
examples, integration tests, ...)?
For unit tests, there is a convention: "main" vs "test".
The latter has no backward-compatibility req
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache Commons Team is pleased to announce the release of Apache
Commons Compress 1.16.1.
Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, tra
On 10 February 2018 at 12:57, Gilles wrote:
> On Sat, 10 Feb 2018 11:52:24 +, sebb wrote:
>>
>> The 3rd party mirrors all offer their services for free.
>>
>> Although storage is cheap these days, it is not free, so we should not
>> burden the mirrors with unnecessary files (*).
>>
>> So would
On Sat, 10 Feb 2018 11:52:24 +, sebb wrote:
The 3rd party mirrors all offer their services for free.
Although storage is cheap these days, it is not free, so we should
not
burden the mirrors with unnecessary files (*).
So would RMs please remember to remove old releases once a new
releas
On 9 February 2018 at 23:08, Bindul Bhowmik wrote:
> On Fri, Feb 9, 2018 at 2:14 PM, Gilles wrote:
>> On Thu, 8 Feb 2018 22:44:32 -0700, Bindul Bhowmik wrote:
>>>
>>> On Thu, Feb 8, 2018 at 9:01 AM, Gilles
>>> wrote:
Hi.
Build succeeds with JDK 7 and 8 but not with JDK9:
The 3rd party mirrors all offer their services for free.
Although storage is cheap these days, it is not free, so we should not
burden the mirrors with unnecessary files (*).
So would RMs please remember to remove old releases once a new release
has been announced.
And when preparing for a new r
On 2018-02-10, Simon Spero wrote:
> Writing tests for osgi modules is painless... the second time :-P
I said I "was pointed into a direction for writing a test ..." that's
been your and Bertrand's input. :-)
> The key to making tests easy is to use pax-exam, which handles most of the
> tedious c
On 2018-02-07, Stefan Bodewig wrote:
> Compress 1.16.1 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/ (svn revision
> 24778)
> The tag is here:
>
> https://git1-us-west.apache.org/repos/asf?p=commons-compress.git;a=tag;h=463d3e7bdcd02d84e565
24 matches
Mail list logo
