Re: [4/4] commons-rng git commit: Moved ProviderBuilder to the base package and made it package private

On Wed, 28 Sep 2016 19:55:21 -0500, Brent Worden wrote: On Wed, Sep 28, 2016 at 6:08 PM, Emmanuel Bourg wrote: Le 28/09/2016 à 17:11, Gilles a écrit : > This what you've done, but it doesn't say why. The class is only used by RandomSource, moving it to the same package

Re: [4/4] commons-rng git commit: Moved ProviderBuilder to the base package and made it package private

On Wed, Sep 28, 2016 at 6:08 PM, Emmanuel Bourg wrote: > Le 28/09/2016 à 17:11, Gilles a écrit : > > > This what you've done, but it doesn't say why. > > The class is only used by RandomSource, moving it to the same package > and marking it package private ensures that it

[RNG] Team work? (Was: ... commit: foreach loops)

On Thu, 29 Sep 2016 01:37:02 +0200, Emmanuel Bourg wrote: Le 28/09/2016 à 17:41, Gilles a écrit : The array indexing was left on purpose (for debugging). Please revert. Well, that wasn't really explicit, I'd suggest putting a comment the next time to materialize your intents. Sorry but

Build failed in Jenkins: commons-beanutils » Apache Commons BeanUtils #16

See Changes: [ggregory] Update japicmp to 0.9.1. -- [...truncated 699 lines...] Exception in thread "main" java.lang.NoClassDefFoundError: ${argLine} Caused

Build failed in Jenkins: commons-beanutils #16

See Changes: [ggregory] Update japicmp to 0.9.1. -- [...truncated 730 lines...] at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at

Re: [RNG] How to write Javadoc (Was: ... commit: Fixed the javadoc errors with Java 8)

I agree that paragraphs should be written like this. Gary On Wed, Sep 28, 2016 at 4:37 PM, Gilles wrote: > > Thanks for the non-trivial details that make the change > understandable. > > It would have been nice to post this information on the ML, > before

[RNG] How to write Javadoc (Was: ... commit: Fixed the javadoc errors with Java 8)

Thanks for the non-trivial details that make the change understandable. It would have been nice to post this information on the ML, before applying the changes. The more so that the issue was encountered by several people in different components, and IIRC now, the consensus (or workaround) had

Re: [2/3] commons-rng git commit: foreach loops

Le 28/09/2016 à 17:41, Gilles a écrit : > The array indexing was left on purpose (for debugging). > Please revert. Well, that wasn't really explicit, I'd suggest putting a comment the next time to materialize your intents. I made another modification to the tests and the index is now reported

Re: [4/4] commons-rng git commit: Moved ProviderBuilder to the base package and made it package private

Le 28/09/2016 à 17:11, Gilles a écrit : > This what you've done, but it doesn't say why. The class is only used by RandomSource, moving it to the same package and marking it package private ensures that it can't be mistakenly used (even if it's marked as internal). Emmanuel Bourg

Re: [1/4] commons-rng git commit: Fixed the javadoc errors with Java 8

Le 28/09/2016 à 16:40, Gilles a écrit : > They are not trivial issues, because they are not seen by everyone. I'm not sure I have the same definition of "trivial" in my dictionary :) > Below, you refer to HTML 5. > > Is the "javadoc" tool assuming that its input is valid HTML 5? Javadoc in

Re: [beanutils] Gradle build weirdness

Ya I got it resolved, the culprit was spring boot plugin. They created their own dependency management within Gradle. The thread is updated with the cause and workaround. On Wed, Sep 28, 2016 at 3:25 PM, Oliver Heger wrote: > > > Am 27.09.2016 um 18:47 schrieb

Re: [beanutils] Gradle build weirdness

Am 27.09.2016 um 18:47 schrieb Raviteja Lokineni: > Does anyone have any fix for it or have experienced the same? Did you get this resolved? I just replaced the dependency in a Maven build, and the new version was picked up immediately. So I think the deployment to Maven central and meta data

[GitHub] commons-io pull request #22: [IO-515] Add constructors that allow the initia...

Github user brettlounsbury closed the pull request at: https://github.com/apache/commons-io/pull/22 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: Regressions in Commons Lang Unit tests when building on Java 9 EA

Hi, as Stefan suggests on https://issues.apache.org/jira/browse/LANG-1265, I think the behavior you've seen is related to http://openjdk.java.net/jeps/252 . If changing the order to prefer CLDR data on Java 8 doesn't lead to the same problem, and changing the order in the JDK 9 EA build

Re: [2/3] commons-rng git commit: foreach loops

Emmanuel, On Wed, 28 Sep 2016 15:05:33 -, ebo...@apache.org wrote: foreach loops The array indexing was left on purpose (for debugging). Please revert. In general, could you please stop these unilateral changes? Some are going to turn out fine, some are not. Most are not trivial to

Re: [lang] Shuffling arrays

On Wed, Sep 28, 2016 at 4:55 PM, Gilles wrote: > Do you mean that CL must define its own interface, say Yes, of course. Btw: Note, that commons-crypto does the same [1]. Jochen 1:

Re: [3/3] commons-rng git commit: Adjusted the alignment of the values in the MT tests

On Wed, 28 Sep 2016 17:22:31 +0200, Emmanuel Bourg wrote: Le 28/09/2016 à 17:17, Gilles a écrit : These numbers were formatted to same width on purpose! Please revert. Actually they weren't in the MT tests. Ah, sorry for that one. Reading "diff" is not funny. I agree that it an

Re: [3/3] commons-rng git commit: Adjusted the alignment of the values in the MT tests

Le 28/09/2016 à 17:17, Gilles a écrit : > These numbers were formatted to same width on purpose! > > Please revert. Actually they weren't in the MT tests. Emmanuel Bourg - To unsubscribe, e-mail:

[MATH] pom.xml: commons.release.version needs to be updated every release

commons.release.version is stuck at 3.4.1. This field needs to be updated prior to a release, the download page regenerated using mvn commons:download-page and the site rebuilt. I have temporarily fixed the live page but the sources need to be fixed as well please. Note: if there is not going

Re: [3/3] commons-rng git commit: Adjusted the alignment of the values in the MT tests

Emmanuel, On Wed, 28 Sep 2016 15:05:34 -, ebo...@apache.org wrote: Adjusted the alignment of the values in the MT tests These numbers were formatted to same width on purpose! Please revert. Gilles Project: http://git-wip-us.apache.org/repos/asf/commons-rng/repo Commit:

Re: [lang] Shuffling arrays

I would expect that we provide implementations of this new interface for all JRE random classes. On Wed, Sep 28, 2016 at 7:55 AM, Gilles wrote: > On Wed, 28 Sep 2016 15:55:34 +0200, Jochen Wiedmann wrote: > >> On Wed, Sep 28, 2016 at 1:40 PM, Gilles

Re: [4/4] commons-rng git commit: Moved ProviderBuilder to the base package and made it package private

Emmanuel, On Wed, 28 Sep 2016 08:54:53 -, ebo...@apache.org wrote: Moved ProviderBuilder to the base package and made it package private This what you've done, but it doesn't say why. I previously noted that I was wary of crippling the Javadoc (if the output would not show up for

Re: [lang] Shuffling arrays

On Wed, 28 Sep 2016 15:55:34 +0200, Jochen Wiedmann wrote: On Wed, Sep 28, 2016 at 1:40 PM, Gilles wrote: If not, then random utilities are not best located in Commons Lang, because indeed the no-dep requirement forces you to go through "java.util.Random" which

Re: [1/4] commons-rng git commit: Fixed the javadoc errors with Java 8

On Wed, 28 Sep 2016 15:39:44 +0200, Emmanuel Bourg wrote: Le 28/09/2016 à 15:06, Gilles a écrit : I use Java 8 and did not get any errors when generating the apidocs. Unless I'm missing something, the above message does not correspond to the change in this commit. The changes themselves

Re: [LANG] Towards 3.5

On Tue, Sep 27, 2016 at 1:36 AM, Charles Honton wrote: > 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. > > I agree with

Re: [RNG] modules vs projects

On Wed, 28 Sep 2016 14:17:19 +0200, Emmanuel Bourg wrote: Le 27/09/2016 à 01:14, Gilles a écrit : An additional module in Commons RNG will not help, as was noticed some time ago: it won't be possible/allowed to release the modules separately. I don't want to have to release a major version of

Re: [lang] Shuffling arrays

On Wed, Sep 28, 2016 at 1:40 PM, Gilles wrote: > If not, then random utilities are not best located in Commons Lang, > because indeed the no-dep requirement forces you to go through > "java.util.Random" which is bad (TM) for several reasons, mentioned > here, there,

Re: [1/4] commons-rng git commit: Fixed the javadoc errors with Java 8

Le 28/09/2016 à 15:06, Gilles a écrit : > I use Java 8 and did not get any errors when generating the apidocs. > > Unless I'm missing something, the above message does not correspond > to the change in this commit. > > The changes themselves contradict usage of the HTML tag: and > enclose a

Re: [lang] Shuffling arrays

On Wed, 28 Sep 2016 13:47:49 +0200, Emmanuel Bourg wrote: Le 28/09/2016 à 13:40, Gilles a écrit : If not, then random utilities are not best located in Commons Lang, because indeed the no-dep requirement forces you to go through "java.util.Random" which is bad (TM) for several reasons,

Re: [1/4] commons-rng git commit: Fixed the javadoc errors with Java 8

Emmanuel, On Wed, 28 Sep 2016 08:54:50 -, ebo...@apache.org wrote: Repository: commons-rng Updated Branches: refs/heads/master fcc9da888 -> fd22dc61f Fixed the javadoc errors with Java 8 I use Java 8 and did not get any errors when generating the apidocs. Unless I'm missing

Re: [RNG] Scope of "Commons RNG"

On Tue, 27 Sep 2016 20:07:19 -0500, Brent Worden wrote: On Mon, Sep 26, 2016 at 11:36 PM, Gilles wrote: On Mon, 26 Sep 2016 21:23:24 -0500, Brent Worden wrote: With that said, I started thinking a bridge to go between the two engines, UniformRandomProvider

Re: [RNG] modules vs projects

Le 27/09/2016 à 01:14, Gilles a écrit : > An additional module in Commons RNG will not help, as was noticed > some time ago: it won't be possible/allowed to release the modules > separately. > > I don't want to have to release a major version of Commons RNG > just because accessory tools

Re: [lang] Shuffling arrays

Le 28/09/2016 à 13:40, Gilles a écrit : > If not, then random utilities are not best located in Commons Lang, > because indeed the no-dep requirement forces you to go through > "java.util.Random" which is bad (TM) for several reasons, mentioned > here, there, and everywhere. I agree

Re: [lang] Shuffling arrays

On Tue, 27 Sep 2016 18:41:59 -0700, Gary Gregory wrote: +1: [lang] is a low-level library, which should not have any deps. This is fine as a requirement. But then why don't you draw all the conclusions from that, including that its scope must be limited, lest the goal is for CL to contain all

[RESULT][VOTE][LAZY] Move Apache Commons EL to dormant

Hi, Benedikt Ritter schrieb am So., 25. Sep. 2016 um 09:59 Uhr: > Hi, > > I think it is time to move the Apache Commons EL component to dormant for > the following reasons: > > - hasn't seen any activity for a long time. > - the 1.0 release dates back longer than 9 years

Re: commons-rng git commit: Requirements for contributing a generator implementation.

Le 22/09/2016 à 14:31, er...@apache.org a écrit : > Repository: commons-rng > Updated Branches: > refs/heads/master 956141c8c -> 41feb7150 > +Please note that a contribution that consists in the implementation of a > +"reference" generator will only be accepted if it comes with Is is possible