There are multiple causes to LANG-1265. The two I have traced look like
incomplete locale/timezone data from the CLDR provider. I recommend moving
forward on 3.5 release without solving LANG-1265.
chas
>> On Sep 26, 2016, at 10:29 AM, Benedikt Ritter wrote:
>>
>> Hi all,
>>
>> as you migh
On Mon, 26 Sep 2016 21:23:24 -0500, Brent Worden wrote:
On Mon, Sep 26, 2016 at 6:21 PM, Gilles
wrote:
On Mon, 26 Sep 2016 16:10:12 -0500, Brent Worden wrote:
I would keep the JDK source. My reasoning being:
1. Users that want to use java.util.Random would not be able to use
some
or
all
On Mon, 26 Sep 2016 21:22:35 -0500, Brent Worden wrote:
First candidates are:
* Non-uniform deviates (i.e. the samplers now defined in
Commons Math's "o.a.c.math4.distribution" package),
I agree this doesn't belong to commons-rng, but I'm not convinced
it
would fit a commons-rng-tools comp
On Mon, Sep 26, 2016 at 6:21 PM, Gilles
wrote:
> On Mon, 26 Sep 2016 16:10:12 -0500, Brent Worden wrote:
>
>> I would keep the JDK source. My reasoning being:
>>
>> 1. Users that want to use java.util.Random would not be able to use some
>> or
>> all of the RNG Utils code as the later will proba
> First candidates are:
>>> * Non-uniform deviates (i.e. the samplers now defined in
>>> Commons Math's "o.a.c.math4.distribution" package),
>>>
>>
>> I agree this doesn't belong to commons-rng, but I'm not convinced it
>> would fit a commons-rng-tools component. Maybe a component more targeted
>
On Mon, 26 Sep 2016 16:10:12 -0500, Brent Worden wrote:
I would keep the JDK source. My reasoning being:
1. Users that want to use java.util.Random would not be able to use
some or
all of the RNG Utils code as the later will probably relay on
RandomSource
instances.
I don't understand the
On Tue, 27 Sep 2016 00:37:26 +0200, Emmanuel Bourg wrote:
Le 26/09/2016 à 18:33, Gilles a écrit :
As I suggested previously on this list, I'm going to request
a new "git" repository for implementing utilities based on
random generators.
I suggest waiting until RNG 1.0 is out and we have a cle
Le 26/09/2016 à 18:33, Gilles a écrit :
> As I suggested previously on this list, I'm going to request
> a new "git" repository for implementing utilities based on
> random generators.
I suggest waiting until RNG 1.0 is out and we have a clearer view of the
scope of the components. We can still e
I would keep the JDK source. My reasoning being:
1. Users that want to use java.util.Random would not be able to use some or
all of the RNG Utils code as the later will probably relay on RandomSource
instances.
2. With LCGs the current Random implementation provided by Oracle could
possibly be e
I'll dig in and have a look at it.
-Rob
> On Sep 26, 2016, at 10:29 AM, Benedikt Ritter wrote:
>
> Hi all,
>
> as you might have noticed, there has been no RC1 on Saturday :-) I've
> decided that I'd like to fix LANG-1265 [1] for 3.5 to have full Java 9
> support. If anybody has some cycles t
Hi.
Reviving this thread following a new feature request:
https://issues.apache.org/jira/browse/RNG-19
IMHO, the request departs from the initial goal (and, hence
the design "requirements" on which the current code is based).
As I suggested previously on this list, I'm going to request
a new
While I will miss the nicer graphics in Clirr I am worried about it
being unmaintained as we are moving towards Java 8 and 9.
Gary found one small issue with japicmp - it requires a "mvn package"
to make a JAR to inspect, thus it fails with just "mvn site" if we
enable it with our src/main/resourc
Hi,
Gary Gregory schrieb am Mo., 26. Sep. 2016 um
17:29 Uhr:
> We have 3 issues:
>
> - Updating the commons-parent to effectively require Java 7 so we can run
> Clirr or an equivalent tool
>
I think this is not an issue, because we have profiles that get activated
for more recent JDKs, which us
We have 3 issues:
- Updating the commons-parent to effectively require Java 7 so we can run
Clirr or an equivalent tool
- Should we still be using Clirr since it is not maintained?
http://clirr.sourceforge.net/ shows "Last published: 27 September 2005 |
Doc for 0.6".
With BeanUtils 1.9.3, we us
Hi all,
as you might have noticed, there has been no RC1 on Saturday :-) I've
decided that I'd like to fix LANG-1265 [1] for 3.5 to have full Java 9
support. If anybody has some cycles to work on this issue, that would be
appreciated.
Thank you!
Benedikt
[1] https://issues.apache.org/jira/browse
Hello Dalibor,
I've noticed several regressions when building the Apache Commons Lang
component with Java 9 EA [1]. I did not have the time yet to investigate
this issues further. Any pointers are appreciated.
Thank you!
Benedikt
[1] https://issues.apache.org/jira/browse/LANG-1265
Stian Soiland-Reyes schrieb am Mo., 26. Sep. 2016 um
15:30 Uhr:
> On 26 September 2016 at 12:59, Stian Soiland-Reyes
> wrote:
> > The Apache Commons team is pleased to announce the release of Apache
> > Commons BeanUtils 1.9.3
>
> Bah.. "Subject: Subject: [ANNOUNCEMENT]" -- hope it still counts
On 26 September 2016 at 12:59, Stian Soiland-Reyes wrote:
> The Apache Commons team is pleased to announce the release of Apache
> Commons BeanUtils 1.9.3
Bah.. "Subject: Subject: [ANNOUNCEMENT]" -- hope it still counts :-(
BTW - all other emails on
https://lists.apache.org/list.html?annou...@ap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache Commons team is pleased to announce the release of Apache
Commons BeanUtils 1.9.3
Apache Commons BeanUtils provides an easy-to-use but flexible wrapper around
reflection and introspection.
commons-beanutils-1.9.3 is a bug fix release, whic
On 23 September 2016 at 19:49, Gary Gregory wrote:
> There is no Clirr report but 'mvn clirr:check' runs OK.
In BeanUtils I used jacoco as clirr-maven-plugin:2.7 fails in JDK8:
[INFO] Generating "Clirr" report--- clirr-maven-plugin:2.7:clirr
[INFO] Comparing to version: 1.9.2
[ER
Le 26/09/2016 à 09:15, Benedikt Ritter a écrit :
> Thank you for the thorough analysis. I agree with your proposal to add
> .htaccess to get the charset right.
+1
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@common
Hello Stian,
Stian Soiland-Reyes schrieb am Mo., 26. Sep. 2016 um
01:45 Uhr:
> As I mentioned in the BeanUtils vote, its RELEASE-NOTES.txt was in
> character set ISO-8859-1, instead of say UTF-8 (to represent the name
> "Tommy Tynjä").
>
> However the RELEASE-NOTES are special in that they go in
22 matches
Mail list logo
