[ANNOUNCE] Commons Parent 48 released.

[This announcement is only going to the dev list.] Hello All, Commons Parent 48 has been released. Changes in this version include: Fixed Bugs: o Revert revert change in commons.scmPubUrl in Parent 47, use commons.packageId for osgi o Revert change in commons.scmPubUrl in Parent 47 Issue:

Re: [imaging] Java 8

So if there are no objections here, the 1.0 RC3 will include Java8 - even if others missed this thread, I will make sure to mention it in the RC3 vote that this is happening, so others can comment if they prefer to keep Java7. Thanks Gary! Bruno On Wednesday, 27 March 2019, 7:32:38 am

Re: [codec] Java 8

If it were easier to maintain branches against various releases of Java, perhaps this wouldn't be as much of an issue. Also, philosophically, I'm already at the point where I consider Java 8 to be the "old" version of Java that's considered a bare minimum, and new/existing projects should be

Re: [codec] Java 8

Indeed. I worked in a bank and in a research company, where in both at least one department was stuck in an old version for issues with the code base or environment policies/decisions. Agree not the best choice, but sometimes developers simply cannot immediately upgrade jvm. Some managers may

Re: [codec] Java 8

This is a good general assumption that legacy installations do not care about new releases, however there is one quite common problem, if they wait for Commons Bugfixes they will be unhappy if a minor Release no longer works in their environment (and they would have to recompile). That’s why I

Re: [codec] Java 8

On Tue, 26 Mar 2019 at 19:01, Matt Sicker wrote: > > I'd like to know what developers are both stuck in Java 7 (or earlier) > and also have the liberty to upgrade any of their dependencies > regardless of compatibility concerns. My thoughts are that being stuck > in the past for one dependency

Re: [codec] Java 8

I'd like to know what developers are both stuck in Java 7 (or earlier) and also have the liberty to upgrade any of their dependencies regardless of compatibility concerns. My thoughts are that being stuck in the past for one dependency tends to leak into every other dependency for the same

Re: [ALL] Maven Magic & Javadoc 9

This might work: https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#jdkToolchain Combine with profiles to activate by default when using jdk 9+. On Tue, 26 Mar 2019 at 13:04, Gary Gregory wrote: > > Hi All: > > Is it possible to tell Maven using the toolchains.xml to use

Re: [imaging] Java 8

On Tue, Mar 26, 2019 at 2:29 PM Bruno P. Kinoshita wrote: > +1 > > Good idea. I think it should be fine as there are other breaking changes > in sanselan -> imaging. > > We loop over data all time in imaging too, some streams/collectors/etc > could make the code more readable. And later maybe

Re: [imaging] Java 8

+1 Good idea. I think it should be fine as there are other breaking changes in sanselan -> imaging. We loop over data all time in imaging too, some streams/collectors/etc could make the code more readable. And later maybe make some of the utility code more functional to be passed around instead

[ANNOUNCEMENT] Apache Commons BCEL 6.3.1

The Apache Commons BCEL team is pleased to announce the release of Apache Commons BCEL 6.3.1! The Byte Code Engineering Library (BCEL) is intended to give users a convenient way to analyze, create, and manipulate compiled .class files. Classes are represented by objects containing all the

[ALL] Maven Magic & Javadoc 9

Hi All: Is it possible to tell Maven using the toolchains.xml to use Java >= 9 if present to run Javadoc? Starting with Java 9, Javadoc creates _searchable_ Javadoc's, the top right of the page has a search box, quite handy. If would be nice to add this to commons-parent. Gary

RE: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

Dear Gilles Sir, Thank you for the feedback! I’ve made the changes as requested. Would you kindly review the document again and check if there are any more final changes required ? And, Alex sir, are there any changes required on the document ? Could you review it too ? Feedback would be highly

[imaging] Java 8

Hi All, I propose we make [imaging] currently 1.0-SNAPSHOT, based on Java 8. I am hoping we can use Java 8's AutoCloseable to make clean up more bullet-proof. Gary

Re: [numbers-fraction] merging changes

Hello Eric. Le mar. 26 mars 2019 à 17:22, Eric Barnhill a écrit : > > I'm rebasing fraction to master and the next merge is looking tricky. > Gilles, am I correct that you have added an interface and some methods to > Fraction, and pushed this to master? I don't think so. Last commit I made to

Re: [All][RNG][Numbers] Broken links on the generated site

Anyone has a clue about those issues? Le jeu. 21 mars 2019 à 16:48, Gilles Sadowski a écrit : > > Hi. > > Somehow, that page contains invalid links (for un/subscribe): > http://commons.apache.org/proper/commons-rng/mailing-lists.html > > Furthermore, the page itself has a different name than

[numbers-fraction] merging changes

I'm rebasing fraction to master and the next merge is looking tricky. Gilles, am I correct that you have added an interface and some methods to Fraction, and pushed this to master? But master does not yet have the of() and from() method name changes that we discussed while my branch does, also my

Re: [codec] RAT check in Jenkins vs local

That’s likely a consequence of this commit: https://github.com/apache/commons-parent/commit/30a0eaea5a3efb14f2e81bcae4aaf06ff9a91bd8 , but I dont’ have a good answer for you on the jenkins build yet. I’ve

Re: New Confluence space created: COMMONS

FYI (Migration of the Moinmoin wiki has been requested). On Mon, Mar 25, 2019 at 8:55 PM ASF Self-Service Platform wrote: > > > Hi there, > As requested by joc...@apache.org, a new Confluence space has been set up at: > https://cwiki.apache.org/confluence/display/COMMONS > > > > With regards, >

Re: [codec] RAT check in Jenkins vs local

My bad, haven't checked rat.txt (was from mobile) bla.tar.xz is not recognized I guess you can report this to rat JIRA and add this file to exclude list to unblock builds ... On Tue, 26 Mar 2019 at 21:25, Maxim Solodovnik wrote: > > Maybe workspace wasn't cleaned and some generated file remain?

Re: [codec] RAT check in Jenkins vs local

Maybe workspace wasn't cleaned and some generated file remain? On Tue, Mar 26, 2019, 21:06 Gary Gregory wrote: > Hi All: > > When I run a RAT check with 'mvn apache-rat:check', all is fine. When I run > the same kind of build as Jenkins with 'mvn clean package', all is fine. > > Why does the

[codec] RAT check in Jenkins vs local

Hi All: When I run a RAT check with 'mvn apache-rat:check', all is fine. When I run the same kind of build as Jenkins with 'mvn clean package', all is fine. Why does the Jenkins build fail its RAT check? https://builds.apache.org/job/Commons-Codec/104/console Gary

Re: [Rng] JDK 11 javadoc support for JPMS modules

Hello. Le lun. 25 mars 2019 à 13:00, Alex Herbert a écrit : > > I managed to get the build working for the site on JDK 11. > > https://github.com/apache/commons-rng/pull/32 > > However left as-is it does not work for the java 9 modules that use JPMS > due to the javadoc tool in JDK 11.0.2. > >

Re: GSoC 19: Information pertaining to 'Lagged Fibonacci Generators'

Thanks for the document. I've made some comments. Let's see whether Alex has something to add. Regards, Gilles Le lun. 25 mars 2019 à 14:30, Abhishek Dhadwal a écrit : > > Dear Sir, > The revised GSoC proposal has been created(minus the about me section), and > the Google Docs link is

Re: GitHub Pull Requests (and Confluence)

Hello Jochen, Am Mo., 25. März 2019 um 16:32 Uhr schrieb Jochen Wiedmann < jochen.wiedm...@gmail.com>: > Hi, > > just FIY: Today I tried to accept a pull request from Github, > following the procedure, as outlined on > > >