Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
On Sat, 31 Dec 2016 00:00:16 + (UTC), Bernd Eckenfels wrote: The issues of the j.u.Random implementation are only for the default implementation, Not true, unfortunately (more than one example in the document). if you provide a different algorithm (from Securearandom or any distribution

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Jörg Schaible
Gilles wrote: > On Fri, 30 Dec 2016 23:05:25 +0100, Gilles wrote: >> On Fri, 30 Dec 2016 20:00:50 +0100, Jörg Schaible wrote: >>> Hi Gilles, >>> >>> Gilles wrote: >>> On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote: > Gilles wrote: > >> Hi. >> >> On Fri, 30 Dec

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Bernd Eckenfels
The issues of the j.u.Random implementation are only for the default implementation, if you provide a different algorithm (from Securearandom or any distribution from RNG) you can avoid it (if needed) Gruss Bernd -- http://bernd.eckenfels.net On Fri, Dec 30, 2016 at 10:50 PM +0100,

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
On Fri, 30 Dec 2016 23:05:25 +0100, Gilles wrote: On Fri, 30 Dec 2016 20:00:50 +0100, Jörg Schaible wrote: Hi Gilles, Gilles wrote: On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote: Gilles wrote: Hi. On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote: Hello all, Personally,

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
On Fri, 30 Dec 2016 20:00:50 +0100, Jörg Schaible wrote: Hi Gilles, Gilles wrote: On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote: Gilles wrote: Hi. On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote: Hello all, Personally, I would like to resolve the TEXT-36 and TEXT-42

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
On Fri, 30 Dec 2016 18:22:37 + (UTC), Bernd Eckenfels wrote: Hello, You suggested to use UniformRandomProvider in TEXT-36. I suggest to use j.u.Random because it is a common (interface like) I know that already. To advance the discussion, could you please comment on the issues in the

Re: [RESULT] Release Compress 1.13 based on RC1

2016-12-30 Thread Gary Gregory
On Thu, Dec 29, 2016 at 2:28 PM, Stefan Bodewig wrote: > On 2016-12-29, Gary Gregory wrote: > > > Did you push to Maven Central too? Just curious. > > Yes, but I got confused by the Nexus UI and managed to "promote" Commons > Parent twice (didn't know this was possible). I

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Jörg Schaible
Hi Gilles, Gilles wrote: > On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote: >> Gilles wrote: >> >>> Hi. >>> >>> On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote: Hello all, Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira tickets before

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Bernd Eckenfels
Hello, You suggested to use UniformRandomProvider in TEXT-36. I suggest to use j.u.Random because it is a common (interface like) type which is easy to provide any alternative random provider you would want (on protected method to implement) - just like InputStream is a commonly subtyped base

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
On Fri, 30 Dec 2016 17:30:17 + (UTC), Bernd Eckenfels wrote: Sorry I meant *uniform* distribution Gruss Bernd On Fri, Dec 30, 2016 at 5:58 PM +0100, "Bernd Eckenfels" wrote: Hello, I am somewhat unclear, why would you require a random distribution

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote: Gilles wrote: Hi. On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote: Hello all, Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira tickets before proceeding with the release, but I wanted to check to see if anyone

Re: [text] 1.0 release progress.

2016-12-30 Thread Gary Gregory
We could add the dep for a 1.1 or 2.0 release but removing the dep would be more painful for users that end up depending on it. The question is: how much benefit do we really get for TEXT from a dep on RNG. Gary On Dec 30, 2016 6:40 AM, "Rob Tompkins" wrote: > Hello all, >

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Bernd Eckenfels
Sorry I meant *uniform* distribution Gruss Bernd On Fri, Dec 30, 2016 at 5:58 PM +0100, "Bernd Eckenfels" wrote: Hello, I am somewhat unclear, why would you require a random distribution (Interface). Is there no better more generic Interface in RNG-API?

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Bernd Eckenfels
Hello, I am somewhat unclear, why would you require a random distribution (Interface). Is there no better more generic Interface in RNG-API? Having said that I still think j.u.Random is fine - but if not maybe a byte or int Provider would be better than a specific interface for the random

Re: [text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Jörg Schaible
Gilles wrote: > Hi. > > On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote: >> Hello all, >> >> Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira >> tickets before proceeding with the release, but I wanted to check to >> see if anyone else has any opinions on what work needs

[text] TEXT-36 (Was: [text] 1.0 release progress)

2016-12-30 Thread Gilles
Hi. On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote: Hello all, Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira tickets before proceeding with the release, but I wanted to check to see if anyone else has any opinions on what work needs to be completed before the

[text] 1.0 release progress.

2016-12-30 Thread Rob Tompkins
Hello all, Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira tickets before proceeding with the release, but I wanted to check to see if anyone else has any opinions on what work needs to be completed before the release. Regarding TEXT-36: 'Dependency on “Commons RNG” ‘, I’m

[ANNOUNCE] Apache Commons JCS 2.0 Released

2016-12-30 Thread Thomas Vandahl
The Apache Commons Team is pleased to announce the availability of: Apache Commons JCS 2.0 Apache Commons JCS is a distributed, versatile caching system. The release notes can be reviewed at: http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt Distribution packages can be downloaded from:

[RESULT][VOTE] Release Apache Commons JCS 2.0 based on RC1

2016-12-30 Thread Thomas Vandahl
On 25.12.16 22:24, Thomas Vandahl wrote: > I would like to release the [jcs] component. > > Apache Commons JCS 2.0 RC1 is available for review at: > https://dist.apache.org/repos/dist/dev/commons/jcs/ (r17574). The following votes were cast (in order of appearance): Thomas Vandahl: +1 Romain

Re: [VOTE] Release Apache Commons JCS 2.0 based on RC1

2016-12-30 Thread Thomas Vandahl
Hi Jörg, On 29.12.16 16:57, Jörg Schaible wrote: > +1 thanks for voting. > builds from source tarball with my compiler zoo except Java 9 (jar-plugin > fails, unrelated to jcs). > > The layout of the binary tarball is somewhat different compared to other > commons releases: > - bin archive