[GitHub] darkma773r opened a new pull request #7: Polar and Spherical Coordinates

[GitBox]

darkma773r opened a new pull request #7: Polar and Spherical Coordinates
URL: https://github.com/apache/commons-geometry/pull/7
 
 
   Adds support for polar and spherical coordinates (GEOMETRY-7).


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-pool issue #10: POOL-347 : Regard waiting object creation as failure...

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/commons-pool/pull/10
  

[![Coverage 
Status](https://coveralls.io/builds/18088758/badge)](https://coveralls.io/builds/18088758)

Coverage increased (+0.1%) to 85.146% when pulling 
**7b3a83479ea3d57c624aa1ecd0260b86b12272de on sunsuk7tp:POOL-347** into 
**3e6dfcd61ddcd88b18934738ebda05c84c948a80 on apache:master**.



---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-pool pull request #10: POOL-347 : Regard waiting object creation as ...

[sunsuk7tp]

GitHub user sunsuk7tp opened a pull request:

https://github.com/apache/commons-pool/pull/10

POOL-347 : Regard waiting object creation as failure if pool is full and 
maxWaitTime passed

JIRA: https://issues.apache.org/jira/browse/POOL-347

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sunsuk7tp/commons-pool POOL-347

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-pool/pull/10.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #10


commit 7b3a83479ea3d57c624aa1ecd0260b86b12272de
Author: Shunsuke Nakamura 
Date:   2018-07-20T16:47:28Z

[POOL-347] Regard waiting object creation as failure if pool is full and 
maxWaitTime passed




---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[RNG] Testing RNG (Was: ... packaging)

[Gilles]

On Fri, 20 Jul 2018 09:29:50 -0600, Gary Gregory wrote:

TL;DR: -1

I do not normally validate an RC one module at a time. Why would you 
do

that?


Who asks?

Also 'install' already does 'package', otherwise, there would be 
nothing to

install, unless you do weird stuff in a POM.


Normally (at least for me), it used to work (i.e. compile, test,
generate all reports) with
 $ mvn -Pcommons-rng-examples site site:stage

I added "package install" in case (?) the new CP and build/release
plugins do "weird stuff" (no idea what that means!). :-)


Running 'mvn clean install' on Java 8 gives me:

[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   ContinuousSamplerParametricTest.testSampling:53->check:127
Ahrens-Dieter Exponential deviate
[rng=org.apache.commons.rng.core.source32.MersenneTwister]: Too many
failures for sample size = 2 (3 out of 50 tests failed, 
chi2=[33.911,

21.6829996, 23.565]
[ERROR]   ContinuousSamplerParametricTest.testSampling:53->check:127
Uniform deviate
[rng=org.apache.commons.rng.core.source64.MersenneTwister64]: Too 
many
failures for sample size = 2 (3 out of 50 tests failed, 
chi2=[22.896,

22.143, 30.6290005]
[INFO]
[ERROR] Tests run: 77, Failures: 2, Errors: 0, Skipped: 0
[INFO]
[INFO]


[INFO] Reactor Summary:
[INFO]
[INFO] Apache Commons RNG 1.1 . SUCCESS [
12.216 s]
[INFO] Apache Commons RNG Client API .. SUCCESS [
4.348 s]
[INFO] Apache Commons RNG Core  SUCCESS [
18.538 s]
[INFO] Apache Commons RNG Simple .. SUCCESS [
12.227 s]
[INFO] Apache Commons RNG Sampling  FAILURE 
[01:24

min]
[INFO] Apache Commons RNG (full distribution) 1.1 . SKIPPED
[INFO]


[INFO] BUILD FAILURE
[INFO]


[INFO] Total time: 02:12 min
[INFO] Finished at: 2018-07-20T09:28:10-06:00
[INFO]



We need a better way to test :-(


As mentioned previously, you'd just need to recall the command
until those unit tests eventually pass.
That they sometimes fail is inherent to the functionality.
But it *may* be that they fail too often, if the unit test
is not tolerant enough (cf. "3 out of 50 tests failed" in
the output). Currently we are on the safe side: being too
lax might hide a fault in the underlying generator.


-1 anyway, because the src zip contains the site-contents folder:

commons-rng-1.1-src/commons-rng-examples/examples-jmh/site-content/ 
and

other site-content folders.

There is no need to bloat the mirrors.

Is this really a Java 6 component, did I see that right?


Yes.


Wow! ;-) We should
move this up to Java 8 after 1.1


There is nothing needed from JDK 7+ in order to add RNG
implementations (only basic operations are used, and the
best implementations are currently less than a dozen lines).
[For 1.0, there was a discussion to bump to Java 7, in order
to use the "multiple exceptions catch" syntax, and it was not
deemed a sufficient reason.]


to make it at least semi-attractive to new
devs.


As opposed to more extent components, AFAICT there is
nothing syntax-wise to be gained from JDK 8+.
Only JPMS (thus JDK 9+) could be a good reason (thus for
application developers, not developers of the component
itself).

Perhaps: if there is the willingness to add a stream API.
[I'd recall that, at the time, the argument was to stay
close to the "java.util.Random" API and not loose a single
percent of speed!]
Even so, streams could easily come as wrappers, defined in
another module targetted to a more recent JDK, without
touching the core implementations.

Gilles


Gary


[...]



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Rob Tompkins]

> On Jul 20, 2018, at 11:29 AM, Gary Gregory  wrote:
> 
> TL;DR: -1
> 
> I do not normally validate an RC one module at a time. Why would you do
> that?
> 
> Also 'install' already does 'package', otherwise, there would be nothing to
> install, unless you do weird stuff in a POM.
> 
> Running 'mvn clean install' on Java 8 gives me:
> 
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR]   ContinuousSamplerParametricTest.testSampling:53->check:127
> Ahrens-Dieter Exponential deviate
> [rng=org.apache.commons.rng.core.source32.MersenneTwister]: Too many
> failures for sample size = 2 (3 out of 50 tests failed, chi2=[33.911,
> 21.6829996, 23.565]
> [ERROR]   ContinuousSamplerParametricTest.testSampling:53->check:127
> Uniform deviate
> [rng=org.apache.commons.rng.core.source64.MersenneTwister64]: Too many
> failures for sample size = 2 (3 out of 50 tests failed, chi2=[22.896,
> 22.143, 30.6290005]
> [INFO]
> [ERROR] Tests run: 77, Failures: 2, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Commons RNG 1.1 . SUCCESS [
> 12.216 s]
> [INFO] Apache Commons RNG Client API .. SUCCESS [
> 4.348 s]
> [INFO] Apache Commons RNG Core  SUCCESS [
> 18.538 s]
> [INFO] Apache Commons RNG Simple .. SUCCESS [
> 12.227 s]
> [INFO] Apache Commons RNG Sampling  FAILURE [01:24
> min]
> [INFO] Apache Commons RNG (full distribution) 1.1 . SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 02:12 min
> [INFO] Finished at: 2018-07-20T09:28:10-06:00
> [INFO]
> 

Just an FYI, this is the non-deterministic test failure. But, yeah I agree with 
what you said below this line.

> 
> We need a better way to test :-(
> 
> -1 anyway, because the src zip contains the site-contents folder:
> 
> commons-rng-1.1-src/commons-rng-examples/examples-jmh/site-content/ and
> other site-content folders.
> 
> There is no need to bloat the mirrors.
> 
> Is this really a Java 6 component, did I see that right? Wow! ;-) We should
> move this up to Java 8 after 1.1 to make it at least semi-attractive to new
> devs.
> 
> Gary
> 
> On Fri, Jul 20, 2018 at 9:03 AM Gilles  wrote:
> 
>> On Fri, 20 Jul 2018 08:54:52 -0600, Gary Gregory wrote:
>>> Is the VOTE still in progress or are you guys debating whether or not
>>> to
>>> cancel  it?
>> 
>> Whether you can run:
>>  $ mvn package install -Pcommons-rng-examples
>> would be a second data point towards that decision. :-)
>> 
>> Gilles
>> 
>>> Gary
>>> 
>>> On Fri, Jul 20, 2018 at 8:46 AM Gilles 
>>> wrote:
>>> 
 On Fri, 20 Jul 2018 09:38:51 -0400, Rob Tompkins wrote:
>> On Jul 20, 2018, at 9:26 AM, Gilles
 
>> wrote:
>> 
>> Hello.
>> 
>> On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
 On Jul 19, 2018, at 8:58 PM, Gilles
 
 wrote:
 
 Hi.
 
 On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
> We have added some significant enhancements since Apache
 Commons
> RNG
> 1.0 was released, so I would like to release Apache Commons
 RNG
> 1.1.
> 
> Apache Commons RNG (full distribution) 1.1 RC2 is available
 for
> review here:
>  https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2
> 
 (svn
> revision 28231)
 
 "commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz":
 Thank
 you!
 
 Is module "dist-archive" now redundant (to be removed)?  [Or
 are
 the
 above files still generated from it?]
>>> 
>>> I’m still using it.
>> 
>> Oh; I thought that it worked the way it is supposed to (IMHO).
 :-{
> 
> It does, I don’t have to cd into the project to get the dist files
 to
> go up to svn; the “mvn … deploy” command works from the root of
 the
> project.
> 
>> 
 
> The Git tag RNG_1_1_RC2 commit for this RC is here:
> 'git  [...] -- [...]' which you can
> browse here:
> 
> 
> 
 
 
>> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
> 
> Maven artifacts are here:
> 
> 
> 
 
 
>> https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus artifact SHA-1s
> 

[CANCEL][VOTE] Release Apache Commons RNG 1.1 based on RC2

[Rob Tompkins]

I’m canceling this [VOTE] because of the src.zip containing more than we want.

-Rob

> On Jul 19, 2018, at 3:21 PM, Rob Tompkins  wrote:
> 
> We have added some significant enhancements since Apache Commons RNG 1.0 was 
> released, so I would like to release Apache Commons RNG 1.1.
> 
> Apache Commons RNG (full distribution) 1.1 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2 (svn revision 
> 28231)
> 
> The Git tag RNG_1_1_RC2 commit for this RC is here:
> 'git  [...] -- [...]' which you can browse here:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
> 
> These are the Maven artifacts and their hashes in Nexus:
> 
> #Nexus artifact SHA-1s
> SHA1(commons-rng-client-api-1.1-javadoc.jar)= 
> 6b00830cab08147e504766a17328a27a95cea712
> SHA1(commons-rng-client-api-1.1-sources.jar)= 
> 2abac2aad66a600dccd261749e9e700bc55edf89
> SHA1(commons-rng-client-api-1.1-test-sources.jar)= 
> a477215706b68a2c45fc96df5f60ff7988056365
> SHA1(commons-rng-client-api-1.1-tests.jar)= 
> 43af258c73539543d18f96cfea75c2564286f18e
> SHA1(commons-rng-client-api-1.1.jar)= 71eb6ac796d2bfc6d6d2330d08b46b8998297982
> SHA1(commons-rng-client-api-1.1.pom)= 26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
> SHA1(commons-rng-core-1.1-javadoc.jar)= 
> 6a98949fcfc1f490e30af49017bcc2868f716da5
> SHA1(commons-rng-core-1.1-sources.jar)= 
> 6b55d976271ae7ad79ded90e32b8575e40e01bfc
> SHA1(commons-rng-core-1.1-test-sources.jar)= 
> 8c03d8b90594a6655903541f0b477f8e3ba8c343
> SHA1(commons-rng-core-1.1-tests.jar)= 9f747af9b20c8c4d70647df38a4323750a0f5800
> SHA1(commons-rng-core-1.1.jar)= a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
> SHA1(commons-rng-core-1.1.pom)= 196e691038f3eb7eb3a45693315b9ca1e4d73e90
> SHA1(commons-rng-parent-1.1-site.xml)= 
> 6e1df36b720e14eed524396107481e509ff42c7c
> SHA1(commons-rng-parent-1.1.pom)= 456203f8707d9f6a927cab51713e078eef126db2
> SHA1(commons-rng-sampling-1.1-javadoc.jar)= 
> 807d78c8fcaab16818d96fd3b8984c7bbe777f31
> SHA1(commons-rng-sampling-1.1-sources.jar)= 
> d94f4f1b64a40e874e324388eb67936b51eae34c
> SHA1(commons-rng-sampling-1.1-test-sources.jar)= 
> b6c62a0c37687906f3d97b9871e8399577805974
> SHA1(commons-rng-sampling-1.1-tests.jar)= 
> fe25a8b485d0e7fb782154a60ccc89ed528220c1
> SHA1(commons-rng-sampling-1.1.jar)= 2a3b034bcc688b444839ed268307e0870b70e38b
> SHA1(commons-rng-sampling-1.1.pom)= 6321863616bf687731d2c3d28fe6ec9c9f340e90
> SHA1(commons-rng-simple-1.1-javadoc.jar)= 
> d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
> SHA1(commons-rng-simple-1.1-sources.jar)= 
> 285ceca8976a89525c484f7656b75e87615653e3
> SHA1(commons-rng-simple-1.1-test-sources.jar)= 
> 35b32201d34a4724cc77c3584e3a0bb0de74210d
> SHA1(commons-rng-simple-1.1-tests.jar)= 
> e5181be4b4314bcea56376234ca962f63c6682b6
> SHA1(commons-rng-simple-1.1.jar)= 3b3cee5833c37eef68b2e976727ad786cf0666f8
> SHA1(commons-rng-simple-1.1.pom)= a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962
> 
> #Release SHA-1s
> #Thu Jul 19 12:47:04 EDT 2018
> commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
> commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
> commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
> commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0
> commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93
> commons-rng-1.1-src-zip.asc=1c90762097b9d352c68cfd0efffef57921a819ce
> commons-rng-1.1-bin-tar.gz=669805ba1e42a0b04f6e4967884e29d408b98cff
> commons-rng-1.1-src-tar.gz.asc=b20bc2a58a2a67cf76b9bf3c8a2f091dc947f54a
> commons-rng-1.1-bin-zip.asc=3eaaa305fdd1a673b0bb1a4bcb8b4bf9a521ac39
> 
> #Release SHA-256s
> #Thu Jul 19 12:47:04 EDT 2018
> commons-rng-1.1-bin-tar.gz.asc=12cc7d1b7fc19004a2ae5aac4e366c76651b595dbc124e34d22012b672faa24e
> commons-rng-1.1-src-zip=a1a4c9e4653dbf0af3f71d97267b71c19065f39cc8fe303a7cd6183e3e755326
> commons-rng-1.1-pom.asc=4fdf05e582fa428f473c0d5aedbce4d1b5cd0d494706d3ae050d06d8631e0776
> commons-rng-1.1-bin-zip=53e855362d9a62b5963525f514647169395f13b12febc0619ec3087915ff3b09
> commons-rng-1.1-src-tar.gz=f23e07e0419fbdf13fd35154f81efc79f09f3f935f82a310c59003c5f2c1
> commons-rng-1.1-src-zip.asc=ca5b76e06336d366a79b05f3ebdf947f42c82bad0964bd87cf04302a206ec975
> commons-rng-1.1-bin-tar.gz=eb743f551b14de9fc7926c33d43a572aa488e3b74c79f15be71907e21f344931
> commons-rng-1.1-src-tar.gz.asc=1cc42fd0d98cd74ce69c7feb1019f6b33bd548317563de0076237ab826bb4288
> commons-rng-1.1-bin-zip.asc=3a836f7a7fe9e72b443692835dd83735031524671885504440b0ecb0a36b48e0
> 
> 
> (no need for .asc hashes!)
> 
> I have tested this with mvn clean install site' using: 
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 
> 2018-06-17T14:33:14-04:00)
> Maven home: /usr/local/Cellar/maven/3.5.4/libexec
> Java version: 1.8.0_172, vendor: Oracle Corporation, runtime: 
> 

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Gary Gregory]

TL;DR: -1

I do not normally validate an RC one module at a time. Why would you do
that?

Also 'install' already does 'package', otherwise, there would be nothing to
install, unless you do weird stuff in a POM.

Running 'mvn clean install' on Java 8 gives me:

[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   ContinuousSamplerParametricTest.testSampling:53->check:127
Ahrens-Dieter Exponential deviate
[rng=org.apache.commons.rng.core.source32.MersenneTwister]: Too many
failures for sample size = 2 (3 out of 50 tests failed, chi2=[33.911,
21.6829996, 23.565]
[ERROR]   ContinuousSamplerParametricTest.testSampling:53->check:127
Uniform deviate
[rng=org.apache.commons.rng.core.source64.MersenneTwister64]: Too many
failures for sample size = 2 (3 out of 50 tests failed, chi2=[22.896,
22.143, 30.6290005]
[INFO]
[ERROR] Tests run: 77, Failures: 2, Errors: 0, Skipped: 0
[INFO]
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Commons RNG 1.1 . SUCCESS [
12.216 s]
[INFO] Apache Commons RNG Client API .. SUCCESS [
4.348 s]
[INFO] Apache Commons RNG Core  SUCCESS [
18.538 s]
[INFO] Apache Commons RNG Simple .. SUCCESS [
12.227 s]
[INFO] Apache Commons RNG Sampling  FAILURE [01:24
min]
[INFO] Apache Commons RNG (full distribution) 1.1 . SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 02:12 min
[INFO] Finished at: 2018-07-20T09:28:10-06:00
[INFO]


We need a better way to test :-(

-1 anyway, because the src zip contains the site-contents folder:

commons-rng-1.1-src/commons-rng-examples/examples-jmh/site-content/ and
other site-content folders.

There is no need to bloat the mirrors.

Is this really a Java 6 component, did I see that right? Wow! ;-) We should
move this up to Java 8 after 1.1 to make it at least semi-attractive to new
devs.

Gary

On Fri, Jul 20, 2018 at 9:03 AM Gilles  wrote:

> On Fri, 20 Jul 2018 08:54:52 -0600, Gary Gregory wrote:
> > Is the VOTE still in progress or are you guys debating whether or not
> > to
> > cancel  it?
>
> Whether you can run:
>   $ mvn package install -Pcommons-rng-examples
> would be a second data point towards that decision. :-)
>
> Gilles
>
> > Gary
> >
> > On Fri, Jul 20, 2018 at 8:46 AM Gilles 
> > wrote:
> >
> >> On Fri, 20 Jul 2018 09:38:51 -0400, Rob Tompkins wrote:
> >> >> On Jul 20, 2018, at 9:26 AM, Gilles
> >> 
> >> >> wrote:
> >> >>
> >> >> Hello.
> >> >>
> >> >> On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
> >>  On Jul 19, 2018, at 8:58 PM, Gilles
> >> 
> >>  wrote:
> >> 
> >>  Hi.
> >> 
> >>  On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
> >> > We have added some significant enhancements since Apache
> >> Commons
> >> > RNG
> >> > 1.0 was released, so I would like to release Apache Commons
> >> RNG
> >> > 1.1.
> >> >
> >> > Apache Commons RNG (full distribution) 1.1 RC2 is available
> >> for
> >> > review here:
> >> >   https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2
> >> > 
> >> (svn
> >> > revision 28231)
> >> 
> >>  "commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz":
> >> Thank
> >>  you!
> >> 
> >>  Is module "dist-archive" now redundant (to be removed)?  [Or
> >> are
> >>  the
> >>  above files still generated from it?]
> >> >>>
> >> >>> I’m still using it.
> >> >>
> >> >> Oh; I thought that it worked the way it is supposed to (IMHO).
> >> :-{
> >> >
> >> > It does, I don’t have to cd into the project to get the dist files
> >> to
> >> > go up to svn; the “mvn … deploy” command works from the root of
> >> the
> >> > project.
> >> >
> >> >>
> >> 
> >> > The Git tag RNG_1_1_RC2 commit for this RC is here:
> >> > 'git  [...] -- [...]' which you can
> >> > browse here:
> >> >
> >> >
> >> >
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
> >> >
> >> > Maven artifacts are here:
> >> >
> >> >
> >> >
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
> >> >
> >> > These are the Maven artifacts and their hashes in Nexus:
> >> >
> >> > #Nexus artifact SHA-1s
> >> > SHA1(commons-rng-client-api-1.1-javadoc.jar)=
> >> > 6b00830cab08147e504766a17328a27a95cea712
> >> > SHA1(commons-rng-client-api-1.1-sources.jar)=
> >> > 2abac2aad66a600dccd261749e9e700bc55edf89
> >> > SHA1(commons-rng-client-api-1.1-test-sources.jar)=
> >> > 

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Gilles]

On Fri, 20 Jul 2018 08:54:52 -0600, Gary Gregory wrote:
Is the VOTE still in progress or are you guys debating whether or not 
to

cancel  it?


Whether you can run:
 $ mvn package install -Pcommons-rng-examples
would be a second data point towards that decision. :-)

Gilles


Gary

On Fri, Jul 20, 2018 at 8:46 AM Gilles  
wrote:



On Fri, 20 Jul 2018 09:38:51 -0400, Rob Tompkins wrote:
>> On Jul 20, 2018, at 9:26 AM, Gilles 


>> wrote:
>>
>> Hello.
>>
>> On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
 On Jul 19, 2018, at 8:58 PM, Gilles 


 wrote:

 Hi.

 On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
> We have added some significant enhancements since Apache 
Commons

> RNG
> 1.0 was released, so I would like to release Apache Commons 
RNG

> 1.1.
>
> Apache Commons RNG (full distribution) 1.1 RC2 is available 
for

> review here:
>   https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2
>  
(svn

> revision 28231)

 "commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz": 
Thank

 you!

 Is module "dist-archive" now redundant (to be removed)?  [Or 
are

 the
 above files still generated from it?]
>>>
>>> I’m still using it.
>>
>> Oh; I thought that it worked the way it is supposed to (IMHO). 
:-{

>
> It does, I don’t have to cd into the project to get the dist files 
to
> go up to svn; the “mvn … deploy” command works from the root of 
the

> project.
>
>>

> The Git tag RNG_1_1_RC2 commit for this RC is here:
> 'git  [...] -- [...]' which you can
> browse here:
>
>
>

https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
>
> Maven artifacts are here:
>
>
>

https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
>
> These are the Maven artifacts and their hashes in Nexus:
>
> #Nexus artifact SHA-1s
> SHA1(commons-rng-client-api-1.1-javadoc.jar)=
> 6b00830cab08147e504766a17328a27a95cea712
> SHA1(commons-rng-client-api-1.1-sources.jar)=
> 2abac2aad66a600dccd261749e9e700bc55edf89
> SHA1(commons-rng-client-api-1.1-test-sources.jar)=
> a477215706b68a2c45fc96df5f60ff7988056365
> SHA1(commons-rng-client-api-1.1-tests.jar)=
> 43af258c73539543d18f96cfea75c2564286f18e
> SHA1(commons-rng-client-api-1.1.jar)=
> 71eb6ac796d2bfc6d6d2330d08b46b8998297982
> SHA1(commons-rng-client-api-1.1.pom)=
> 26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
> SHA1(commons-rng-core-1.1-javadoc.jar)=
> 6a98949fcfc1f490e30af49017bcc2868f716da5
> SHA1(commons-rng-core-1.1-sources.jar)=
> 6b55d976271ae7ad79ded90e32b8575e40e01bfc
> SHA1(commons-rng-core-1.1-test-sources.jar)=
> 8c03d8b90594a6655903541f0b477f8e3ba8c343
> SHA1(commons-rng-core-1.1-tests.jar)=
> 9f747af9b20c8c4d70647df38a4323750a0f5800
> SHA1(commons-rng-core-1.1.jar)=
> a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
> SHA1(commons-rng-core-1.1.pom)=
> 196e691038f3eb7eb3a45693315b9ca1e4d73e90
> SHA1(commons-rng-parent-1.1-site.xml)=
> 6e1df36b720e14eed524396107481e509ff42c7c
> SHA1(commons-rng-parent-1.1.pom)=
> 456203f8707d9f6a927cab51713e078eef126db2
> SHA1(commons-rng-sampling-1.1-javadoc.jar)=
> 807d78c8fcaab16818d96fd3b8984c7bbe777f31
> SHA1(commons-rng-sampling-1.1-sources.jar)=
> d94f4f1b64a40e874e324388eb67936b51eae34c
> SHA1(commons-rng-sampling-1.1-test-sources.jar)=
> b6c62a0c37687906f3d97b9871e8399577805974
> SHA1(commons-rng-sampling-1.1-tests.jar)=
> fe25a8b485d0e7fb782154a60ccc89ed528220c1
> SHA1(commons-rng-sampling-1.1.jar)=
> 2a3b034bcc688b444839ed268307e0870b70e38b
> SHA1(commons-rng-sampling-1.1.pom)=
> 6321863616bf687731d2c3d28fe6ec9c9f340e90
> SHA1(commons-rng-simple-1.1-javadoc.jar)=
> d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
> SHA1(commons-rng-simple-1.1-sources.jar)=
> 285ceca8976a89525c484f7656b75e87615653e3
> SHA1(commons-rng-simple-1.1-test-sources.jar)=
> 35b32201d34a4724cc77c3584e3a0bb0de74210d
> SHA1(commons-rng-simple-1.1-tests.jar)=
> e5181be4b4314bcea56376234ca962f63c6682b6
> SHA1(commons-rng-simple-1.1.jar)=
> 3b3cee5833c37eef68b2e976727ad786cf0666f8
> SHA1(commons-rng-simple-1.1.pom)=
> a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962
>
> #Release SHA-1s
> #Thu Jul 19 12:47:04 EDT 2018
>
>

commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
> 
commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
> 
commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
> 
commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0

>
> 
commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93

>
> 

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Gary Gregory]

Is the VOTE still in progress or are you guys debating whether or not to
cancel  it?

Gary

On Fri, Jul 20, 2018 at 8:46 AM Gilles  wrote:

> On Fri, 20 Jul 2018 09:38:51 -0400, Rob Tompkins wrote:
> >> On Jul 20, 2018, at 9:26 AM, Gilles 
> >> wrote:
> >>
> >> Hello.
> >>
> >> On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
>  On Jul 19, 2018, at 8:58 PM, Gilles 
>  wrote:
> 
>  Hi.
> 
>  On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
> > We have added some significant enhancements since Apache Commons
> > RNG
> > 1.0 was released, so I would like to release Apache Commons RNG
> > 1.1.
> >
> > Apache Commons RNG (full distribution) 1.1 RC2 is available for
> > review here:
> >   https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2
> >  (svn
> > revision 28231)
> 
>  "commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz": Thank
>  you!
> 
>  Is module "dist-archive" now redundant (to be removed)?  [Or are
>  the
>  above files still generated from it?]
> >>>
> >>> I’m still using it.
> >>
> >> Oh; I thought that it worked the way it is supposed to (IMHO). :-{
> >
> > It does, I don’t have to cd into the project to get the dist files to
> > go up to svn; the “mvn … deploy” command works from the root of the
> > project.
> >
> >>
> 
> > The Git tag RNG_1_1_RC2 commit for this RC is here:
> > 'git  [...] -- [...]' which you can
> > browse here:
> >
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
> >
> > Maven artifacts are here:
> >
> >
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
> >
> > These are the Maven artifacts and their hashes in Nexus:
> >
> > #Nexus artifact SHA-1s
> > SHA1(commons-rng-client-api-1.1-javadoc.jar)=
> > 6b00830cab08147e504766a17328a27a95cea712
> > SHA1(commons-rng-client-api-1.1-sources.jar)=
> > 2abac2aad66a600dccd261749e9e700bc55edf89
> > SHA1(commons-rng-client-api-1.1-test-sources.jar)=
> > a477215706b68a2c45fc96df5f60ff7988056365
> > SHA1(commons-rng-client-api-1.1-tests.jar)=
> > 43af258c73539543d18f96cfea75c2564286f18e
> > SHA1(commons-rng-client-api-1.1.jar)=
> > 71eb6ac796d2bfc6d6d2330d08b46b8998297982
> > SHA1(commons-rng-client-api-1.1.pom)=
> > 26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
> > SHA1(commons-rng-core-1.1-javadoc.jar)=
> > 6a98949fcfc1f490e30af49017bcc2868f716da5
> > SHA1(commons-rng-core-1.1-sources.jar)=
> > 6b55d976271ae7ad79ded90e32b8575e40e01bfc
> > SHA1(commons-rng-core-1.1-test-sources.jar)=
> > 8c03d8b90594a6655903541f0b477f8e3ba8c343
> > SHA1(commons-rng-core-1.1-tests.jar)=
> > 9f747af9b20c8c4d70647df38a4323750a0f5800
> > SHA1(commons-rng-core-1.1.jar)=
> > a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
> > SHA1(commons-rng-core-1.1.pom)=
> > 196e691038f3eb7eb3a45693315b9ca1e4d73e90
> > SHA1(commons-rng-parent-1.1-site.xml)=
> > 6e1df36b720e14eed524396107481e509ff42c7c
> > SHA1(commons-rng-parent-1.1.pom)=
> > 456203f8707d9f6a927cab51713e078eef126db2
> > SHA1(commons-rng-sampling-1.1-javadoc.jar)=
> > 807d78c8fcaab16818d96fd3b8984c7bbe777f31
> > SHA1(commons-rng-sampling-1.1-sources.jar)=
> > d94f4f1b64a40e874e324388eb67936b51eae34c
> > SHA1(commons-rng-sampling-1.1-test-sources.jar)=
> > b6c62a0c37687906f3d97b9871e8399577805974
> > SHA1(commons-rng-sampling-1.1-tests.jar)=
> > fe25a8b485d0e7fb782154a60ccc89ed528220c1
> > SHA1(commons-rng-sampling-1.1.jar)=
> > 2a3b034bcc688b444839ed268307e0870b70e38b
> > SHA1(commons-rng-sampling-1.1.pom)=
> > 6321863616bf687731d2c3d28fe6ec9c9f340e90
> > SHA1(commons-rng-simple-1.1-javadoc.jar)=
> > d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
> > SHA1(commons-rng-simple-1.1-sources.jar)=
> > 285ceca8976a89525c484f7656b75e87615653e3
> > SHA1(commons-rng-simple-1.1-test-sources.jar)=
> > 35b32201d34a4724cc77c3584e3a0bb0de74210d
> > SHA1(commons-rng-simple-1.1-tests.jar)=
> > e5181be4b4314bcea56376234ca962f63c6682b6
> > SHA1(commons-rng-simple-1.1.jar)=
> > 3b3cee5833c37eef68b2e976727ad786cf0666f8
> > SHA1(commons-rng-simple-1.1.pom)=
> > a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962
> >
> > #Release SHA-1s
> > #Thu Jul 19 12:47:04 EDT 2018
> >
> >
> commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
> > commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
> > commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
> > commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0
> >
> > commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93
> >
> > 

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Gilles]

On Fri, 20 Jul 2018 09:38:51 -0400, Rob Tompkins wrote:
On Jul 20, 2018, at 9:26 AM, Gilles  
wrote:


Hello.

On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
On Jul 19, 2018, at 8:58 PM, Gilles  
wrote:


Hi.

On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
We have added some significant enhancements since Apache Commons 
RNG
1.0 was released, so I would like to release Apache Commons RNG 
1.1.


Apache Commons RNG (full distribution) 1.1 RC2 is available for 
review here:
  https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2 
 (svn

revision 28231)


"commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz": Thank 
you!


Is module "dist-archive" now redundant (to be removed)?  [Or are 
the

above files still generated from it?]


I’m still using it.


Oh; I thought that it worked the way it is supposed to (IMHO). :-{


It does, I don’t have to cd into the project to get the dist files to
go up to svn; the “mvn … deploy” command works from the root of the
project.






The Git tag RNG_1_1_RC2 commit for this RC is here:
'git  [...] -- [...]' which you can 
browse here:



https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2

Maven artifacts are here:


https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/

These are the Maven artifacts and their hashes in Nexus:

#Nexus artifact SHA-1s
SHA1(commons-rng-client-api-1.1-javadoc.jar)=
6b00830cab08147e504766a17328a27a95cea712
SHA1(commons-rng-client-api-1.1-sources.jar)=
2abac2aad66a600dccd261749e9e700bc55edf89
SHA1(commons-rng-client-api-1.1-test-sources.jar)=
a477215706b68a2c45fc96df5f60ff7988056365
SHA1(commons-rng-client-api-1.1-tests.jar)=
43af258c73539543d18f96cfea75c2564286f18e
SHA1(commons-rng-client-api-1.1.jar)=
71eb6ac796d2bfc6d6d2330d08b46b8998297982
SHA1(commons-rng-client-api-1.1.pom)=
26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
SHA1(commons-rng-core-1.1-javadoc.jar)=
6a98949fcfc1f490e30af49017bcc2868f716da5
SHA1(commons-rng-core-1.1-sources.jar)=
6b55d976271ae7ad79ded90e32b8575e40e01bfc
SHA1(commons-rng-core-1.1-test-sources.jar)=
8c03d8b90594a6655903541f0b477f8e3ba8c343
SHA1(commons-rng-core-1.1-tests.jar)=
9f747af9b20c8c4d70647df38a4323750a0f5800
SHA1(commons-rng-core-1.1.jar)= 
a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
SHA1(commons-rng-core-1.1.pom)= 
196e691038f3eb7eb3a45693315b9ca1e4d73e90

SHA1(commons-rng-parent-1.1-site.xml)=
6e1df36b720e14eed524396107481e509ff42c7c
SHA1(commons-rng-parent-1.1.pom)= 
456203f8707d9f6a927cab51713e078eef126db2

SHA1(commons-rng-sampling-1.1-javadoc.jar)=
807d78c8fcaab16818d96fd3b8984c7bbe777f31
SHA1(commons-rng-sampling-1.1-sources.jar)=
d94f4f1b64a40e874e324388eb67936b51eae34c
SHA1(commons-rng-sampling-1.1-test-sources.jar)=
b6c62a0c37687906f3d97b9871e8399577805974
SHA1(commons-rng-sampling-1.1-tests.jar)=
fe25a8b485d0e7fb782154a60ccc89ed528220c1
SHA1(commons-rng-sampling-1.1.jar)= 
2a3b034bcc688b444839ed268307e0870b70e38b
SHA1(commons-rng-sampling-1.1.pom)= 
6321863616bf687731d2c3d28fe6ec9c9f340e90

SHA1(commons-rng-simple-1.1-javadoc.jar)=
d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
SHA1(commons-rng-simple-1.1-sources.jar)=
285ceca8976a89525c484f7656b75e87615653e3
SHA1(commons-rng-simple-1.1-test-sources.jar)=
35b32201d34a4724cc77c3584e3a0bb0de74210d
SHA1(commons-rng-simple-1.1-tests.jar)=
e5181be4b4314bcea56376234ca962f63c6682b6
SHA1(commons-rng-simple-1.1.jar)= 
3b3cee5833c37eef68b2e976727ad786cf0666f8
SHA1(commons-rng-simple-1.1.pom)= 
a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962


#Release SHA-1s
#Thu Jul 19 12:47:04 EDT 2018

commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0

commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93

commons-rng-1.1-src-zip.asc=1c90762097b9d352c68cfd0efffef57921a819ce

commons-rng-1.1-bin-tar.gz=669805ba1e42a0b04f6e4967884e29d408b98cff

commons-rng-1.1-src-tar.gz.asc=b20bc2a58a2a67cf76b9bf3c8a2f091dc947f54a

commons-rng-1.1-bin-zip.asc=3eaaa305fdd1a673b0bb1a4bcb8b4bf9a521ac39

#Release SHA-256s
#Thu Jul 19 12:47:04 EDT 2018

commons-rng-1.1-bin-tar.gz.asc=12cc7d1b7fc19004a2ae5aac4e366c76651b595dbc124e34d22012b672faa24e

commons-rng-1.1-src-zip=a1a4c9e4653dbf0af3f71d97267b71c19065f39cc8fe303a7cd6183e3e755326

commons-rng-1.1-pom.asc=4fdf05e582fa428f473c0d5aedbce4d1b5cd0d494706d3ae050d06d8631e0776

commons-rng-1.1-bin-zip=53e855362d9a62b5963525f514647169395f13b12febc0619ec3087915ff3b09

commons-rng-1.1-src-tar.gz=f23e07e0419fbdf13fd35154f81efc79f09f3f935f82a310c59003c5f2c1

commons-rng-1.1-src-zip.asc=ca5b76e06336d366a79b05f3ebdf947f42c82bad0964bd87cf04302a206ec975

commons-rng-1.1-bin-tar.gz=eb743f551b14de9fc7926c33d43a572aa488e3b74c79f15be71907e21f344931

Re: [COLLECTIONS] Drop all but 4.2 from mirrors?

[Gary Gregory]

On Fri, Jul 20, 2018 at 8:05 AM sebb  wrote:

> On 20 July 2018 at 14:03, Gary Gregory  wrote:
> > I thought we were keeping it around since it is a different major
> version.
>
> Maybe originally, but now I doubt it's needed.
>
> > I am fine with removing it. But that means we need to update the site
> > download page as well.
>
> I am happy to do that.
>

Great, thanks Sebb.

Gary


>
> > Gary
> >
> > On Fri, Jul 20, 2018, 02:59 sebb  wrote:
> >
> >> Are we going to make any fixes to 3.2.x line?
> >>
> >> I really doubt it, so the code should be removed from the mirrors and
> >> the download page.
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [COLLECTIONS] Drop all but 4.2 from mirrors?

[sebb]

On 20 July 2018 at 14:03, Gary Gregory  wrote:
> I thought we were keeping it around since it is a different major version.

Maybe originally, but now I doubt it's needed.

> I am fine with removing it. But that means we need to update the site
> download page as well.

I am happy to do that.

> Gary
>
> On Fri, Jul 20, 2018, 02:59 sebb  wrote:
>
>> Are we going to make any fixes to 3.2.x line?
>>
>> I really doubt it, so the code should be removed from the mirrors and
>> the download page.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Rob Tompkins]

> On Jul 20, 2018, at 9:26 AM, Gilles  wrote:
> 
> Hello.
> 
> On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
>>> On Jul 19, 2018, at 8:58 PM, Gilles  wrote:
>>> 
>>> Hi.
>>> 
>>> On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
 We have added some significant enhancements since Apache Commons RNG
 1.0 was released, so I would like to release Apache Commons RNG 1.1.
 
 Apache Commons RNG (full distribution) 1.1 RC2 is available for review 
 here:
   https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2 
  (svn
 revision 28231)
>>> 
>>> "commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz": Thank you!
>>> 
>>> Is module "dist-archive" now redundant (to be removed)?  [Or are the
>>> above files still generated from it?]
>> 
>> I’m still using it.
> 
> Oh; I thought that it worked the way it is supposed to (IMHO). :-{

It does, I don’t have to cd into the project to get the dist files to go up to 
svn; the “mvn … deploy” command works from the root of the project.

> 
>>> 
 The Git tag RNG_1_1_RC2 commit for this RC is here:
 'git  [...] -- [...]' which you can browse here:
 
 https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
 
 Maven artifacts are here:
 
 https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
 
 These are the Maven artifacts and their hashes in Nexus:
 
 #Nexus artifact SHA-1s
 SHA1(commons-rng-client-api-1.1-javadoc.jar)=
 6b00830cab08147e504766a17328a27a95cea712
 SHA1(commons-rng-client-api-1.1-sources.jar)=
 2abac2aad66a600dccd261749e9e700bc55edf89
 SHA1(commons-rng-client-api-1.1-test-sources.jar)=
 a477215706b68a2c45fc96df5f60ff7988056365
 SHA1(commons-rng-client-api-1.1-tests.jar)=
 43af258c73539543d18f96cfea75c2564286f18e
 SHA1(commons-rng-client-api-1.1.jar)=
 71eb6ac796d2bfc6d6d2330d08b46b8998297982
 SHA1(commons-rng-client-api-1.1.pom)=
 26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
 SHA1(commons-rng-core-1.1-javadoc.jar)=
 6a98949fcfc1f490e30af49017bcc2868f716da5
 SHA1(commons-rng-core-1.1-sources.jar)=
 6b55d976271ae7ad79ded90e32b8575e40e01bfc
 SHA1(commons-rng-core-1.1-test-sources.jar)=
 8c03d8b90594a6655903541f0b477f8e3ba8c343
 SHA1(commons-rng-core-1.1-tests.jar)=
 9f747af9b20c8c4d70647df38a4323750a0f5800
 SHA1(commons-rng-core-1.1.jar)= a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
 SHA1(commons-rng-core-1.1.pom)= 196e691038f3eb7eb3a45693315b9ca1e4d73e90
 SHA1(commons-rng-parent-1.1-site.xml)=
 6e1df36b720e14eed524396107481e509ff42c7c
 SHA1(commons-rng-parent-1.1.pom)= 456203f8707d9f6a927cab51713e078eef126db2
 SHA1(commons-rng-sampling-1.1-javadoc.jar)=
 807d78c8fcaab16818d96fd3b8984c7bbe777f31
 SHA1(commons-rng-sampling-1.1-sources.jar)=
 d94f4f1b64a40e874e324388eb67936b51eae34c
 SHA1(commons-rng-sampling-1.1-test-sources.jar)=
 b6c62a0c37687906f3d97b9871e8399577805974
 SHA1(commons-rng-sampling-1.1-tests.jar)=
 fe25a8b485d0e7fb782154a60ccc89ed528220c1
 SHA1(commons-rng-sampling-1.1.jar)= 
 2a3b034bcc688b444839ed268307e0870b70e38b
 SHA1(commons-rng-sampling-1.1.pom)= 
 6321863616bf687731d2c3d28fe6ec9c9f340e90
 SHA1(commons-rng-simple-1.1-javadoc.jar)=
 d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
 SHA1(commons-rng-simple-1.1-sources.jar)=
 285ceca8976a89525c484f7656b75e87615653e3
 SHA1(commons-rng-simple-1.1-test-sources.jar)=
 35b32201d34a4724cc77c3584e3a0bb0de74210d
 SHA1(commons-rng-simple-1.1-tests.jar)=
 e5181be4b4314bcea56376234ca962f63c6682b6
 SHA1(commons-rng-simple-1.1.jar)= 3b3cee5833c37eef68b2e976727ad786cf0666f8
 SHA1(commons-rng-simple-1.1.pom)= a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962
 
 #Release SHA-1s
 #Thu Jul 19 12:47:04 EDT 2018
 commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
 commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
 commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
 commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0
 commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93
 commons-rng-1.1-src-zip.asc=1c90762097b9d352c68cfd0efffef57921a819ce
 commons-rng-1.1-bin-tar.gz=669805ba1e42a0b04f6e4967884e29d408b98cff
 commons-rng-1.1-src-tar.gz.asc=b20bc2a58a2a67cf76b9bf3c8a2f091dc947f54a
 commons-rng-1.1-bin-zip.asc=3eaaa305fdd1a673b0bb1a4bcb8b4bf9a521ac39
 
 #Release SHA-256s
 #Thu Jul 19 12:47:04 EDT 2018
 commons-rng-1.1-bin-tar.gz.asc=12cc7d1b7fc19004a2ae5aac4e366c76651b595dbc124e34d22012b672faa24e
 commons-rng-1.1-src-zip=a1a4c9e4653dbf0af3f71d97267b71c19065f39cc8fe303a7cd6183e3e755326
 commons-rng-1.1-pom.asc=4fdf05e582fa428f473c0d5aedbce4d1b5cd0d494706d3ae050d06d8631e0776
 

Re: [rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Gilles]

Hello.

On Fri, 20 Jul 2018 08:59:05 -0400, Rob Tompkins wrote:
On Jul 19, 2018, at 8:58 PM, Gilles  
wrote:


Hi.

On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
We have added some significant enhancements since Apache Commons 
RNG
1.0 was released, so I would like to release Apache Commons RNG 
1.1.


Apache Commons RNG (full distribution) 1.1 RC2 is available for 
review here:
   https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2 
 (svn

revision 28231)


"commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz": Thank 
you!


Is module "dist-archive" now redundant (to be removed)?  [Or are the
above files still generated from it?]


I’m still using it.


Oh; I thought that it worked the way it is supposed to (IMHO). :-{




The Git tag RNG_1_1_RC2 commit for this RC is here:
'git  [...] -- [...]' which you can browse 
here:



https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2

Maven artifacts are here:


https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/

These are the Maven artifacts and their hashes in Nexus:

#Nexus artifact SHA-1s
SHA1(commons-rng-client-api-1.1-javadoc.jar)=
6b00830cab08147e504766a17328a27a95cea712
SHA1(commons-rng-client-api-1.1-sources.jar)=
2abac2aad66a600dccd261749e9e700bc55edf89
SHA1(commons-rng-client-api-1.1-test-sources.jar)=
a477215706b68a2c45fc96df5f60ff7988056365
SHA1(commons-rng-client-api-1.1-tests.jar)=
43af258c73539543d18f96cfea75c2564286f18e
SHA1(commons-rng-client-api-1.1.jar)=
71eb6ac796d2bfc6d6d2330d08b46b8998297982
SHA1(commons-rng-client-api-1.1.pom)=
26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
SHA1(commons-rng-core-1.1-javadoc.jar)=
6a98949fcfc1f490e30af49017bcc2868f716da5
SHA1(commons-rng-core-1.1-sources.jar)=
6b55d976271ae7ad79ded90e32b8575e40e01bfc
SHA1(commons-rng-core-1.1-test-sources.jar)=
8c03d8b90594a6655903541f0b477f8e3ba8c343
SHA1(commons-rng-core-1.1-tests.jar)=
9f747af9b20c8c4d70647df38a4323750a0f5800
SHA1(commons-rng-core-1.1.jar)= 
a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
SHA1(commons-rng-core-1.1.pom)= 
196e691038f3eb7eb3a45693315b9ca1e4d73e90

SHA1(commons-rng-parent-1.1-site.xml)=
6e1df36b720e14eed524396107481e509ff42c7c
SHA1(commons-rng-parent-1.1.pom)= 
456203f8707d9f6a927cab51713e078eef126db2

SHA1(commons-rng-sampling-1.1-javadoc.jar)=
807d78c8fcaab16818d96fd3b8984c7bbe777f31
SHA1(commons-rng-sampling-1.1-sources.jar)=
d94f4f1b64a40e874e324388eb67936b51eae34c
SHA1(commons-rng-sampling-1.1-test-sources.jar)=
b6c62a0c37687906f3d97b9871e8399577805974
SHA1(commons-rng-sampling-1.1-tests.jar)=
fe25a8b485d0e7fb782154a60ccc89ed528220c1
SHA1(commons-rng-sampling-1.1.jar)= 
2a3b034bcc688b444839ed268307e0870b70e38b
SHA1(commons-rng-sampling-1.1.pom)= 
6321863616bf687731d2c3d28fe6ec9c9f340e90

SHA1(commons-rng-simple-1.1-javadoc.jar)=
d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
SHA1(commons-rng-simple-1.1-sources.jar)=
285ceca8976a89525c484f7656b75e87615653e3
SHA1(commons-rng-simple-1.1-test-sources.jar)=
35b32201d34a4724cc77c3584e3a0bb0de74210d
SHA1(commons-rng-simple-1.1-tests.jar)=
e5181be4b4314bcea56376234ca962f63c6682b6
SHA1(commons-rng-simple-1.1.jar)= 
3b3cee5833c37eef68b2e976727ad786cf0666f8
SHA1(commons-rng-simple-1.1.pom)= 
a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962


#Release SHA-1s
#Thu Jul 19 12:47:04 EDT 2018

commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0
commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93

commons-rng-1.1-src-zip.asc=1c90762097b9d352c68cfd0efffef57921a819ce
commons-rng-1.1-bin-tar.gz=669805ba1e42a0b04f6e4967884e29d408b98cff

commons-rng-1.1-src-tar.gz.asc=b20bc2a58a2a67cf76b9bf3c8a2f091dc947f54a

commons-rng-1.1-bin-zip.asc=3eaaa305fdd1a673b0bb1a4bcb8b4bf9a521ac39

#Release SHA-256s
#Thu Jul 19 12:47:04 EDT 2018

commons-rng-1.1-bin-tar.gz.asc=12cc7d1b7fc19004a2ae5aac4e366c76651b595dbc124e34d22012b672faa24e

commons-rng-1.1-src-zip=a1a4c9e4653dbf0af3f71d97267b71c19065f39cc8fe303a7cd6183e3e755326

commons-rng-1.1-pom.asc=4fdf05e582fa428f473c0d5aedbce4d1b5cd0d494706d3ae050d06d8631e0776

commons-rng-1.1-bin-zip=53e855362d9a62b5963525f514647169395f13b12febc0619ec3087915ff3b09

commons-rng-1.1-src-tar.gz=f23e07e0419fbdf13fd35154f81efc79f09f3f935f82a310c59003c5f2c1

commons-rng-1.1-src-zip.asc=ca5b76e06336d366a79b05f3ebdf947f42c82bad0964bd87cf04302a206ec975

commons-rng-1.1-bin-tar.gz=eb743f551b14de9fc7926c33d43a572aa488e3b74c79f15be71907e21f344931

commons-rng-1.1-src-tar.gz.asc=1cc42fd0d98cd74ce69c7feb1019f6b33bd548317563de0076237ab826bb4288

commons-rng-1.1-bin-zip.asc=3a836f7a7fe9e72b443692835dd83735031524671885504440b0ecb0a36b48e0


(no need for .asc hashes!)

I have tested this with mvn clean install site' using:
Apache Maven 3.5.4 

Re: [COLLECTIONS] Drop all but 4.2 from mirrors?

[Gary Gregory]

I thought we were keeping it around since it is a different major version.
I am fine with removing it. But that means we need to update the site
download page as well.

Gary

On Fri, Jul 20, 2018, 02:59 sebb  wrote:

> Are we going to make any fixes to 3.2.x line?
>
> I really doubt it, so the code should be removed from the mirrors and
> the download page.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[rng] packaging (Was: Re: [VOTE] Release Apache Commons RNG 1.1 based on RC2)

[Rob Tompkins]

> On Jul 19, 2018, at 8:58 PM, Gilles  wrote:
> 
> Hi.
> 
> On Thu, 19 Jul 2018 15:21:28 -0400, Rob Tompkins wrote:
>> We have added some significant enhancements since Apache Commons RNG
>> 1.0 was released, so I would like to release Apache Commons RNG 1.1.
>> 
>> Apache Commons RNG (full distribution) 1.1 RC2 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/rng/1.1-RC2 
>>  (svn
>> revision 28231)
> 
> "commons-rng-1.1-bin.zip" and "commons-rng-1.1-bin.tar.gz": Thank you!
> 
> Is module "dist-archive" now redundant (to be removed)?  [Or are the
> above files still generated from it?]

I’m still using it.

> 
>> The Git tag RNG_1_1_RC2 commit for this RC is here:
>> 'git  [...] -- [...]' which you can browse here:
>> 
>> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tag;h=refs/tags/RNG_1_1_RC2
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1352/org/apache/commons/
>> 
>> These are the Maven artifacts and their hashes in Nexus:
>> 
>> #Nexus artifact SHA-1s
>> SHA1(commons-rng-client-api-1.1-javadoc.jar)=
>> 6b00830cab08147e504766a17328a27a95cea712
>> SHA1(commons-rng-client-api-1.1-sources.jar)=
>> 2abac2aad66a600dccd261749e9e700bc55edf89
>> SHA1(commons-rng-client-api-1.1-test-sources.jar)=
>> a477215706b68a2c45fc96df5f60ff7988056365
>> SHA1(commons-rng-client-api-1.1-tests.jar)=
>> 43af258c73539543d18f96cfea75c2564286f18e
>> SHA1(commons-rng-client-api-1.1.jar)=
>> 71eb6ac796d2bfc6d6d2330d08b46b8998297982
>> SHA1(commons-rng-client-api-1.1.pom)=
>> 26ec84056b9a4526bc5e05ecf4ece8d9c3d57aad
>> SHA1(commons-rng-core-1.1-javadoc.jar)=
>> 6a98949fcfc1f490e30af49017bcc2868f716da5
>> SHA1(commons-rng-core-1.1-sources.jar)=
>> 6b55d976271ae7ad79ded90e32b8575e40e01bfc
>> SHA1(commons-rng-core-1.1-test-sources.jar)=
>> 8c03d8b90594a6655903541f0b477f8e3ba8c343
>> SHA1(commons-rng-core-1.1-tests.jar)=
>> 9f747af9b20c8c4d70647df38a4323750a0f5800
>> SHA1(commons-rng-core-1.1.jar)= a4b491d5bbe0d398e4453d4bd0255eb1e707e3c9
>> SHA1(commons-rng-core-1.1.pom)= 196e691038f3eb7eb3a45693315b9ca1e4d73e90
>> SHA1(commons-rng-parent-1.1-site.xml)=
>> 6e1df36b720e14eed524396107481e509ff42c7c
>> SHA1(commons-rng-parent-1.1.pom)= 456203f8707d9f6a927cab51713e078eef126db2
>> SHA1(commons-rng-sampling-1.1-javadoc.jar)=
>> 807d78c8fcaab16818d96fd3b8984c7bbe777f31
>> SHA1(commons-rng-sampling-1.1-sources.jar)=
>> d94f4f1b64a40e874e324388eb67936b51eae34c
>> SHA1(commons-rng-sampling-1.1-test-sources.jar)=
>> b6c62a0c37687906f3d97b9871e8399577805974
>> SHA1(commons-rng-sampling-1.1-tests.jar)=
>> fe25a8b485d0e7fb782154a60ccc89ed528220c1
>> SHA1(commons-rng-sampling-1.1.jar)= 2a3b034bcc688b444839ed268307e0870b70e38b
>> SHA1(commons-rng-sampling-1.1.pom)= 6321863616bf687731d2c3d28fe6ec9c9f340e90
>> SHA1(commons-rng-simple-1.1-javadoc.jar)=
>> d1f10e032078ab73f202cac2aa90fb7e80cf5d4a
>> SHA1(commons-rng-simple-1.1-sources.jar)=
>> 285ceca8976a89525c484f7656b75e87615653e3
>> SHA1(commons-rng-simple-1.1-test-sources.jar)=
>> 35b32201d34a4724cc77c3584e3a0bb0de74210d
>> SHA1(commons-rng-simple-1.1-tests.jar)=
>> e5181be4b4314bcea56376234ca962f63c6682b6
>> SHA1(commons-rng-simple-1.1.jar)= 3b3cee5833c37eef68b2e976727ad786cf0666f8
>> SHA1(commons-rng-simple-1.1.pom)= a3f7a09914ba4b7dfc2a28fec5d7a40f3f1ea962
>> 
>> #Release SHA-1s
>> #Thu Jul 19 12:47:04 EDT 2018
>> commons-rng-1.1-bin-tar.gz.asc=c3f836de906655a83a8e2a3728393378829f2116
>> commons-rng-1.1-src-zip=e667b1b7f1409dbdc809f0aeeeabb0bc48bef331
>> commons-rng-1.1-pom.asc=ff1f921acebd92ce1cab7d63a60cfcf0498da77a
>> commons-rng-1.1-bin-zip=ea19ddac066eead6d8230e3508a084491fd9e2e0
>> commons-rng-1.1-src-tar.gz=e89aa1f0146f06f09380ff5ef59447164b9b7d93
>> commons-rng-1.1-src-zip.asc=1c90762097b9d352c68cfd0efffef57921a819ce
>> commons-rng-1.1-bin-tar.gz=669805ba1e42a0b04f6e4967884e29d408b98cff
>> commons-rng-1.1-src-tar.gz.asc=b20bc2a58a2a67cf76b9bf3c8a2f091dc947f54a
>> commons-rng-1.1-bin-zip.asc=3eaaa305fdd1a673b0bb1a4bcb8b4bf9a521ac39
>> 
>> #Release SHA-256s
>> #Thu Jul 19 12:47:04 EDT 2018
>> commons-rng-1.1-bin-tar.gz.asc=12cc7d1b7fc19004a2ae5aac4e366c76651b595dbc124e34d22012b672faa24e
>> commons-rng-1.1-src-zip=a1a4c9e4653dbf0af3f71d97267b71c19065f39cc8fe303a7cd6183e3e755326
>> commons-rng-1.1-pom.asc=4fdf05e582fa428f473c0d5aedbce4d1b5cd0d494706d3ae050d06d8631e0776
>> commons-rng-1.1-bin-zip=53e855362d9a62b5963525f514647169395f13b12febc0619ec3087915ff3b09
>> commons-rng-1.1-src-tar.gz=f23e07e0419fbdf13fd35154f81efc79f09f3f935f82a310c59003c5f2c1
>> commons-rng-1.1-src-zip.asc=ca5b76e06336d366a79b05f3ebdf947f42c82bad0964bd87cf04302a206ec975
>> commons-rng-1.1-bin-tar.gz=eb743f551b14de9fc7926c33d43a572aa488e3b74c79f15be71907e21f344931
>> commons-rng-1.1-src-tar.gz.asc=1cc42fd0d98cd74ce69c7feb1019f6b33bd548317563de0076237ab826bb4288
>> 

Re: [LANG] Java 9 problems because of dependencies to java.desktop

[Gilles]

Hi.

On Fri, 20 Jul 2018 09:47:21 +0100, sebb wrote:

On 20 July 2018 at 00:09, Bruno P. Kinoshita
 wrote:

What is the replacement for Observer/Observable recommended by
the JDK developers?
I believe they suggest to use the PropertyListener which we have 
right now, but are in the java.beans module I think.
Alternatively, they also suggest in the javadocs to look into the 
java.util.concurrent package if concurrency is important.


From what I understand about the latter option, it would mean 
building your own event-bus or listeners.


I've read that Observer/Observable will not be removed from the
JDK (but won't be maintained).  So, if the shortcomings are OK
for the purpose at hand, the issue is only the deprecation warning.

Does someone readily knows how to go about implementing an equivalent
functionality with "java.util.concurrent" classes?

Regards,
Gilles

As for the java.beans, a possible solution to avoid deprecation 
right now would be include the java.beans property listeners code in 
[lang]. Maybe internal only.


AFAIK we cannot copy any JVM code into our codebase, even if marked 
internal.

It would have to be a clean-room implementation.


Bruno

  From: Gilles 
 To: dev@commons.apache.org
 Sent: Friday, 20 July 2018 11:05 AM
 Subject: Re: [LANG] Java 9 problems because of dependencies to 
java.desktop


Hello.

On Mon, 16 Jul 2018 21:30:00 + (UTC), Bruno P. Kinoshita wrote:
What about introducing our own state listener interface? The 
original

interface from the beans package was used just for convenience
because
it already existed. But it would of course be possible to have a
simple
functional interface to notify listeners about state changes.

Hmmm, that's an option as well.
Looks like they had the beans interface which we used, then later 
we
had the java.util.Observable for a while, and now they are 
suggesting

users to move to the beans interface, as one of the alternatives.
As some Java 9 users possibly wouldn't want to import the 
java.beans

module, perhaps having this new interface could be an interesting
alternative.
I believe we would have to
[ ] decide whether to introduce an interface similar to
PropertyListener, or to Observable[ ] if the backward compatibility
changed, we must deprecate the existing classes
[ ] release a new version of lang with this new interface and the
updated circuit breakers[ ] and either delete the deprecated 
classes

or leave it until for some more releases
I wonder what others think about this option?


What is the replacement for Observer/Observable recommended by
the JDK developers?

Regards,
Gilles


Cheers
Bruno


 From: Oliver Heger 
 To: dev@commons.apache.org
 Sent: Tuesday, 17 July 2018 4:13 AM
 Subject: Re: [LANG] Java 9 problems because of dependencies to
java.desktop (Was: Re: [LANG] Thoughts about Lang 4.0)



Am 16.07.2018 um 13:40 schrieb Bruno P. Kinoshita:
Saw some recent activity around lang 3.8, and remembered about 
this

issue, and then looked for this thread.

Gilles' point is really good! Here's the Java 9 docs with the
deprecation warning, copied below as well

https://docs.oracle.com/javase/9/docs/api/index.html?java/util/Observable.html


"This class and the Observer interface have been deprecated. The
event model supported by Observer and Observable is quite limited, 
the

order of notifications delivered by Observable is unspecified, and
state changes are not in one-for-one correspondence with
notifications. For a richer event model, consider using the 
java.beans
package.  For reliable and ordered messaging among threads, 
consider

using one of the concurrent data structures in the
java.util.concurrent package. For reactive streams style 
programming,

see the Flow API."



So I guess the best we can do right now is add the @deprecated
annotations, with an explanation in the javadocs. And also add a 
note

about it in the release notes.

Does that sound like a good plan? Adding a link to this thread in
the pull request as well.



What about introducing our own state listener interface? The 
original

interface from the beans package was used just for convenience
because
it already existed. But it would of course be possible to have a
simple
functional interface to notify listeners about state changes.

Oliver



Cheers
Bruno





From: Stephen Colebourne 
To: Commons Developers List 
Sent: Monday, 11 June 2018 9:26 AM
Subject: Re: [LANG] Java 9 problems because of dependencies to
java.desktop (Was: Re: [LANG] Thoughts about Lang 4.0)



Good spot. I think that means [lang] would have to have its own 
copy

of the JDK interfaces. or just deprecate the functionality without
replacement.
Stephen

On 10 June 2018 at 22:11, Gilles 
wrote:

Hello.

On Sun, 10 Jun 2018 21:34:49 +0200, Oliver Heger wrote:


Hi Bruno,

Am 10.06.2018 um 00:52 schrieb Bruno P. Kinoshita:


Hi all,

There is a patch [1] for LANG-1339 [2] that I would like to
merge. The
discussion around this issue 

[COLLECTIONS] Drop all but 4.2 from mirrors?

[sebb]

Are we going to make any fixes to 3.2.x line?

I really doubt it, so the code should be removed from the mirrors and
the download page.

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [LANG] Java 9 problems because of dependencies to java.desktop

[sebb]

On 20 July 2018 at 00:09, Bruno P. Kinoshita
 wrote:
>>What is the replacement for Observer/Observable recommended by
>>the JDK developers?
> I believe they suggest to use the PropertyListener which we have right now, 
> but are in the java.beans module I think.
> Alternatively, they also suggest in the javadocs to look into the 
> java.util.concurrent package if concurrency is important.
>
> From what I understand about the latter option, it would mean building your 
> own event-bus or listeners.
> As for the java.beans, a possible solution to avoid deprecation right now 
> would be include the java.beans property listeners code in [lang]. Maybe 
> internal only.

AFAIK we cannot copy any JVM code into our codebase, even if marked internal.
It would have to be a clean-room implementation.

> Bruno
>
>   From: Gilles 
>  To: dev@commons.apache.org
>  Sent: Friday, 20 July 2018 11:05 AM
>  Subject: Re: [LANG] Java 9 problems because of dependencies to java.desktop
>
> Hello.
>
> On Mon, 16 Jul 2018 21:30:00 + (UTC), Bruno P. Kinoshita wrote:
>>>What about introducing our own state listener interface? The original
>>>interface from the beans package was used just for convenience
>>> because
>>>it already existed. But it would of course be possible to have a
>>> simple
>>>functional interface to notify listeners about state changes.
>> Hmmm, that's an option as well.
>> Looks like they had the beans interface which we used, then later we
>> had the java.util.Observable for a while, and now they are suggesting
>> users to move to the beans interface, as one of the alternatives.
>> As some Java 9 users possibly wouldn't want to import the java.beans
>> module, perhaps having this new interface could be an interesting
>> alternative.
>> I believe we would have to
>> [ ] decide whether to introduce an interface similar to
>> PropertyListener, or to Observable[ ] if the backward compatibility
>> changed, we must deprecate the existing classes
>> [ ] release a new version of lang with this new interface and the
>> updated circuit breakers[ ] and either delete the deprecated classes
>> or leave it until for some more releases
>> I wonder what others think about this option?
>
> What is the replacement for Observer/Observable recommended by
> the JDK developers?
>
> Regards,
> Gilles
>
>> Cheers
>> Bruno
>>
>>
>>  From: Oliver Heger 
>>  To: dev@commons.apache.org
>>  Sent: Tuesday, 17 July 2018 4:13 AM
>>  Subject: Re: [LANG] Java 9 problems because of dependencies to
>> java.desktop (Was: Re: [LANG] Thoughts about Lang 4.0)
>>
>>
>>
>> Am 16.07.2018 um 13:40 schrieb Bruno P. Kinoshita:
>>> Saw some recent activity around lang 3.8, and remembered about this
>>> issue, and then looked for this thread.
>>>
>>> Gilles' point is really good! Here's the Java 9 docs with the
>>> deprecation warning, copied below as well
>>> https://docs.oracle.com/javase/9/docs/api/index.html?java/util/Observable.html
>>>
>>>
>>> "This class and the Observer interface have been deprecated. The
>>> event model supported by Observer and Observable is quite limited, the
>>> order of notifications delivered by Observable is unspecified, and
>>> state changes are not in one-for-one correspondence with
>>> notifications. For a richer event model, consider using the java.beans
>>> package.  For reliable and ordered messaging among threads, consider
>>> using one of the concurrent data structures in the
>>> java.util.concurrent package. For reactive streams style programming,
>>> see the Flow API."
>>>
>>>
>>>
>>> So I guess the best we can do right now is add the @deprecated
>>> annotations, with an explanation in the javadocs. And also add a note
>>> about it in the release notes.
>>>
>>> Does that sound like a good plan? Adding a link to this thread in
>>> the pull request as well.
>>>
>>
>> What about introducing our own state listener interface? The original
>> interface from the beans package was used just for convenience
>> because
>> it already existed. But it would of course be possible to have a
>> simple
>> functional interface to notify listeners about state changes.
>>
>> Oliver
>>
>>>
>>> Cheers
>>> Bruno
>>>
>>>
>>>
>>>
>>> 
>>> From: Stephen Colebourne 
>>> To: Commons Developers List 
>>> Sent: Monday, 11 June 2018 9:26 AM
>>> Subject: Re: [LANG] Java 9 problems because of dependencies to
>>> java.desktop (Was: Re: [LANG] Thoughts about Lang 4.0)
>>>
>>>
>>>
>>> Good spot. I think that means [lang] would have to have its own copy
>>> of the JDK interfaces. or just deprecate the functionality without
>>> replacement.
>>> Stephen
>>>
>>> On 10 June 2018 at 22:11, Gilles 
>>> wrote:
 Hello.

 On Sun, 10 Jun 2018 21:34:49 +0200, Oliver Heger wrote:
>
> Hi Bruno,
>
> Am 10.06.2018 um 00:52 schrieb Bruno P. Kinoshita:
>>
>> Hi all,
>>
>> There is a patch [1] for LANG-1339 [2] that I would like to
>> merge. The
>> discussion around this