Re: Compiler targets and Java 9

> On Jun 5, 2017, at 2:58 PM, Ralph Goers wrote: > > >> On Jun 5, 2017, at 1:00 PM, Amey Jadiye wrote: >> >> correct, moving to Java9 might be restricting 1.5 to run on higher >> versions, that said they may not run on java 9 so all this

[GitHub] commons-compress issue #26: COMPRESS-399 OSGI package versions are overly pe...

Github user sesuncedu commented on the issue: https://github.com/apache/commons-compress/pull/26 A key point is that these files that are not modified for each release. They are only changed when the package version changes, which only happens when the API changes (and was

[GitHub] commons-compress issue #26: COMPRESS-399 OSGI package versions are overly pe...

Github user joehni commented on the issue: https://github.com/apache/commons-compress/pull/26 ... and again we have a bunch of files that we have to modify for every release. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

Re: Compiler targets and Java 9

On Mon, Jun 5, 2017 at 2:56 PM, Ralph Goers wrote: > > > On Jun 5, 2017, at 1:35 PM, sebb wrote: > > > > On 5 June 2017 at 21:06, Ralph Goers > wrote: > >> OK. Who cares if their last

Re: [NUMBERS] Proposal for refactoring and extension of Gamma functions.

On Tue, 6 Jun 2017 01:14:38 +0530, Amey Jadiye wrote: Hi All, Coming from discussion happened here https://issues.apache.org/jira/browse/NUMBERS-38 As Gamma is nothing but advanced factorial function gamma(n)=(n-1)! with advantages like we can have factorial of whole numbers as well as

Re: Compiler targets and Java 9

> On Jun 5, 2017, at 1:00 PM, Amey Jadiye wrote: > > correct, moving to Java9 might be restricting 1.5 to run on higher > versions, that said they may not run on java 9 so all this discussion came > in picture, I wish we can have java 9 target well at the same time we >

Re: Compiler targets and Java 9

> On Jun 5, 2017, at 1:35 PM, sebb wrote: > > On 5 June 2017 at 21:06, Ralph Goers > wrote: >> OK. Who cares if their last release was Java 1.5? They will never release >> another version that supports it. > >

Re: [all] Deploying components

I have used bin zips before to get to DLL files for example. Gary On Jun 5, 2017 9:58 AM, "Stian Soiland-Reyes" wrote: > Personally I am happy about source distributions accompanying the jars in > Maven Central, which are actually rebuildable as opposed to the > -source.jars.

Re: Compiler targets and Java 9

On 5 June 2017 at 21:06, Ralph Goers wrote: > OK. Who cares if their last release was Java 1.5? They will never release > another version that supports it. Not sure who you mean by 'they' here. This thread is about Commons components whose latest release is 1.5 or

[GitHub] commons-compress pull request #27: COMPRESS-400

GitHub user sesuncedu opened a pull request: https://github.com/apache/commons-compress/pull/27 COMPRESS-400 Add extra header map to tar archive entry. Move PAX header processing code from TarArchiveInputStream to TarAchiveEntry. Use same code for processing user supplied

Re: Compiler targets and Java 9

OK. Who cares if their last release was Java 1.5? They will never release another version that supports it. Ralph > On Jun 5, 2017, at 12:55 PM, sebb wrote: > > On 5 June 2017 at 20:26, Amey Jadiye > wrote: >> +1 >> >> I

Re: Compiler targets and Java 9

correct, moving to Java9 might be restricting 1.5 to run on higher versions, that said they may not run on java 9 so all this discussion came in picture, I wish we can have java 9 target well at the same time we should detach our self from java 1.5, just a view. Regards, Amey On Tue, Jun 6, 2017

Re: Compiler targets and Java 9

On 5 June 2017 at 20:26, Amey Jadiye wrote: > +1 > > I have seen hundreds of applications which are in (maintenance+ little > enhancement) mode are already moved to higher versions of java ( >1.5 ), > even very legacy applications which are just in maintenance mode or marked

[NUMBERS] Proposal for refactoring and extension of Gamma functions.

Hi All, Coming from discussion happened here https://issues.apache.org/jira/browse/NUMBERS-38 As Gamma is nothing but advanced factorial function gamma(n)=(n-1)! with advantages like we can have factorial of whole numbers as well as factional. Now as [Gamma functions (

Re: Compiler targets and Java 9

+1 I have seen hundreds of applications which are in (maintenance+ little enhancement) mode are already moved to higher versions of java ( >1.5 ), even very legacy applications which are just in maintenance mode or marked for decommission are already running on 1.6 as all know that there will be

Re: Compiler targets and Java 9

I'm confused about one thing here. Sure, you can't use javac in 9 to compile for 5, but can't java in 9 still run class files compiled against 5? If you couldn't run older java classes anymore, then I don't know why Oracle continues to maintain backward compatibility in places that are annoying.

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user ameyjadiye commented on the issue: https://github.com/apache/commons-text/pull/44 Hi @garydgregory , Its already discussed here [LANG-564](https://issues.apache.org/jira/browse/LANG-564) and [TEXT-80](https://issues.apache.org/jira/browse/TEXT-80) and all seems agree on

Re: [all] Deploying components

Personally I am happy about source distributions accompanying the jars in Maven Central, which are actually rebuildable as opposed to the -source.jars. they continue to be retrievable using Maven version mechanisms, compares to more fragile scripts crawling archive.apache.org (dist only contains

Re: Compiler targets and Java 9

This whole discussion has me really confused. According to https://en.wikipedia.org/wiki/Java_version_history the free version of Java 5 reached end-of-life in 2009 and Oracle's supported version reached end-of-life in 2015.

Re: [all] Should our gitignore files contain only build-related entries?

Are we talking about only the Maven profile or also about the Java profile. I find that one overly eager and why does it contain BlueJ IDE (only)? Gruss Bernd -- http://bernd.eckenfels.net From: sebb Sent: Monday, June 5, 2017 5:09:18 PM To:

Re: Compiler targets and Java 9

On Mon, Jun 5, 2017 at 9:17 AM, Jochen Wiedmann wrote: > On Mon, Jun 5, 2017 at 5:20 PM, sebb wrote: > > >> I'd like us to be able to push out a new release with minimal changes > >> at any given time. If we have, for example, 1.6 as the target, and

Re: Compiler targets and Java 9

On Mon, Jun 5, 2017 at 8:20 AM, sebb wrote: > On 5 June 2017 at 16:09, Jochen Wiedmann > wrote: > > On Mon, Jun 5, 2017 at 5:06 PM, sebb wrote: > > > >>> I'd like us to push out a new release with minimal changes at any > >>> time.

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user garydgregory commented on the issue: https://github.com/apache/commons-text/pull/44 BTW, this will break source compatibility for certain. --- 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

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user garydgregory commented on the issue: https://github.com/apache/commons-text/pull/44 Hi All, Why is it confusing? Why is the patch better? You get the idea, you have to make a point that what you propose is better beyond changing source. Gary --- If your

Re: Compiler targets and Java 9

On 5 June 2017 at 17:17, Jochen Wiedmann wrote: > On Mon, Jun 5, 2017 at 5:20 PM, sebb wrote: > >>> I'd like us to be able to push out a new release with minimal changes >>> at any given time. If we have, for example, 1.6 as the target, and the >>>

Re: Compiler targets and Java 9

On Mon, Jun 5, 2017 at 5:20 PM, sebb wrote: >> I'd like us to be able to push out a new release with minimal changes >> at any given time. If we have, for example, 1.6 as the target, and the >> previous >> release had 1.5 as the target, then we'd loose that ability, IMO. >>

Re: Compiler targets and Java 9

On 5 June 2017 at 16:09, Jochen Wiedmann wrote: > On Mon, Jun 5, 2017 at 5:06 PM, sebb wrote: > >>> I'd like us to push out a new release with minimal changes at any >>> time. If we have, for example, 1.6 as the target, and the previous >>> release

Re: [VOTE][LAZY] Migrate Apache Commons CLI to git

+1 Gary On Jun 5, 2017 4:20 AM, "Benedikt Ritter" wrote: > Hi, > > I’d like to call a vote by lazy consensus for migrating the code base of > Apache Commons CLI to git. > > This vote is successful if nobody raises objections within the next 72 > hours, e.g. until

Re: [all] Should our gitignore files contain only build-related entries?

On 5 June 2017 at 11:20, Benedikt Ritter wrote: > Hi, > > I usually only use what gibo [1] generates. I don’t put editor specific > entries into .gitignore for my personal projects. This stuff should go into > your personal gitignore. If developers don’t know about global

Re: Compiler targets and Java 9

On Mon, Jun 5, 2017 at 5:06 PM, sebb wrote: >> I'd like us to push out a new release with minimal changes at any >> time. If we have, for example, 1.6 as the target, and the previous >> release had 1.5 as the target, then we'd loose that ability, IMO. > > Sorry, I don't follow.

Re: Compiler targets and Java 9

On 5 June 2017 at 15:54, Jochen Wiedmann wrote: > On Mon, Jun 5, 2017 at 4:50 PM, Emmanuel Bourg wrote: > >> +1 for using 1.6 as the baseline, but I don't see the need to publish >> new releases with that target if nothing else changed. +1 for 1.6

Re: [all] Deploying components

On 5 June 2017 at 12:06, Benedikt Ritter wrote: > Hello Rob, > >> Am 28.05.2017 um 03:01 schrieb Rob Tompkins : >> >> Hello all, >> >> Benedikt and I were chatting last week about how the .tar and .zip >> distributions get uploaded to nexus during "mvn

Re: Compiler targets and Java 9

On Mon, Jun 5, 2017 at 4:50 PM, Emmanuel Bourg wrote: > +1 for using 1.6 as the baseline, but I don't see the need to publish > new releases with that target if nothing else changed. I'd like us to push out a new release with minimal changes at any time. If we have, for

Re: [LANG] Fix date related test failures on IBM JDKs (Was: Re: [CANCEL][VOTE] Release Apache Commons Lang 3.6 based on RC2)

>From what I recall, the IBM JDK is only for Linux and Windows. On 5 June 2017 at 05:54, Benedikt Ritter wrote: > Hi, > > > Am 25.05.2017 um 13:16 schrieb sebb : > > > > On 25 May 2017 at 01:02, Gary Gregory >

Re: Compiler targets and Java 9

Le 5/06/2017 à 16:41, Jochen Wiedmann a écrit : > All commons proper components are expected within one year from now on > to bump their compiler target to 1.6, or beyond, and have a release > published with that target. That way, we know, that it works fine with > the Java 9 compiler. +1 for

Compiler targets and Java 9

Hi, thanks to Rob Rompkins, and his recent work on Fileupload, it came to my attention that Java 9 will no longer support JVM 1.5, and lower, as a compiler target. [1] This means, that we will be preventing our developers from using Java 9, if a component is still below 1.6. (And, I'd expect

Re: [VOTE][LAZY] Migrate Apache Commons CLI to git

Ah .. Thanks for the knowledge, got confused with this url git:// git.apache.org/commons-cli.git +1 for migration. Regards, Amey On Mon, Jun 5, 2017, 7:16 PM Rob Tompkins wrote: > > > On Jun 5, 2017, at 9:39 AM, Amey Jadiye wrote: > > > > Hi, > > >

Re: [PARENT][PROPOSAL] Add Automatic-Module-Name MANIFEST entry

> On Jun 5, 2017, at 4:34 AM, Benedikt Ritter wrote: > > Hi, > >> Am 03.06.2017 um 18:54 schrieb Rob Tompkins > >: >> >> This should be done now with the entries being “commons.module.name” > > I’d recommend using dashes in

Re: [TEXT]: No Github to commons-dev ML connectivity.

> On Jun 5, 2017, at 4:48 AM, Benedikt Ritter wrote: > > Hi, > >> Am 02.06.2017 um 21:44 schrieb Amey Jadiye : >> >> Hi, >> >> I have observed many mails from commons lang, fileupload, cli, compress >> and many other modules where if someone opened

Re: [VOTE][LAZY] Migrate Apache Commons CLI to git

> On Jun 5, 2017, at 9:39 AM, Amey Jadiye wrote: > > Hi, > > I already see it's on github [1] which is mirror of Apache repository [2]. > Is my understanding correct or am I missing something here ? > > > [1] https://github.com/apache/commons-cli > [2]

[GitHub] commons-text pull request #43: [Junit]: Added test cases for CsvTranslators

Github user asfgit closed the pull request at: https://github.com/apache/commons-text/pull/43 --- 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 feature

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user chtompki commented on the issue: https://github.com/apache/commons-text/pull/44 Would this imply a 2.0 release because of BC compatibility? --- 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

Re: [VOTE][LAZY] Migrate Apache Commons CLI to git

Hi, I already see it's on github [1] which is mirror of Apache repository [2]. Is my understanding correct or am I missing something here ? [1] https://github.com/apache/commons-cli [2] git://git.apache.org/commons-cli.git Regards, Amey On Mon, Jun 5, 2017, 4:50 PM Benedikt Ritter

Re: [all] Deploying components

> On Jun 5, 2017, at 7:06 AM, Benedikt Ritter wrote: > > Hello Rob, > >> Am 28.05.2017 um 03:01 schrieb Rob Tompkins : >> >> Hello all, >> >> Benedikt and I were chatting last week about how the .tar and .zip >> distributions get uploaded to nexus

[VOTE][LAZY] Migrate Apache Commons CLI to git

Hi, I’d like to call a vote by lazy consensus for migrating the code base of Apache Commons CLI to git. This vote is successful if nobody raises objections within the next 72 hours, e.g. until June-08-2017, 13:30 MESZ. Regards, Benedikt

Re: [lang] Appetite for new method StringUtils.toCamelCase(String str, char delimiter, boolean capitalizeFirstLetter)

+1 I like the way of implementation, I think we should have class in Commons text CaseUtils.toCamelCase(String str, char delimiter, boolean capitalizeFirstLetter) Also this can have api for snake case (not sure if java need it) @chtompki , If you wish I will submit code for review. Regards,

Re: [all] Deploying components

Hello Rob, > Am 28.05.2017 um 03:01 schrieb Rob Tompkins : > > Hello all, > > Benedikt and I were chatting last week about how the .tar and .zip > distributions get uploaded to nexus during "mvn deploy” and how annoying that > side effect of the deployment happens to be.

[LANG] Fix date related test failures on IBM JDKs (Was: Re: [CANCEL][VOTE] Release Apache Commons Lang 3.6 based on RC2)

Hi, > Am 25.05.2017 um 13:16 schrieb sebb : > > On 25 May 2017 at 01:02, Gary Gregory > wrote: >> On Wed, May 24, 2017 at 4:46 PM, Gary Gregory >> wrote: >> >>> On Wed, May 24, 2017 at 2:12 PM,

[LANG] Java 9 problems because of dependencies to java.desktop (Was: Re: [LANG] Thoughts about Lang 4.0)

> Am 25.05.2017 um 18:23 schrieb Oliver Heger : > > > > Am 24.05.2017 um 13:55 schrieb Stephen Colebourne: >> On 23 May 2017 at 17:17, sebb wrote: Yes, the code compiles and both can be on the classpath, but it is a pain to use,

Re: [ALL] Video recordings of Apache Commons presentations at ApacheCON 2017 in Miami

Hi, > Am 26.05.2017 um 08:17 schrieb Gary Gregory : > > Hi All, > > These talks are great; well done guys! I encourage all to watch :-) And I encourage all to join as at the next ApacheCON :-) > > Gary > > On Sun, May 21, 2017 at 4:40 PM, Benedikt Ritter

Re: [collections] Uniform null-safe methods in CollectionUtils

Hello Bruno, > Am 27.05.2017 um 15:40 schrieb Bruno P. Kinoshita > : > > Hi, > > COLLECTIONS-600 [1] received a pull request [2] to make a method in > CollectionUtils null-safe. Before merging it, I decided to check what was the > current approach in this

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user britter commented on the issue: https://github.com/apache/commons-text/pull/44 LGTM, @chtompki what do you think? --- 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

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user ameyjadiye commented on the issue: https://github.com/apache/commons-text/pull/44 @britter , please review and accept this PR. Travis build on this is because previous commit in master , by merging this won't make any issue in master. Tested on local before creating PR.

Re: [TEXT]: No Github to commons-dev ML connectivity.

Hello Amey, > Am 05.06.2017 um 12:20 schrieb Amey Jadiye : > > Thanks for the help Benedikt. The issue has just been resolved by infra. So the notifications should be working now. Regards, Benedikt > > Regards, > Amey > > > On Jun 5, 2017 2:18 PM, "Benedikt Ritter"

Re: [TEXT]: No Github to commons-dev ML connectivity.

Thanks for the help Benedikt. Regards, Amey On Jun 5, 2017 2:18 PM, "Benedikt Ritter" wrote: Hi, > Am 02.06.2017 um 21:44 schrieb Amey Jadiye : > > Hi, > > I have observed many mails from commons lang, fileupload, cli, compress > and many other

Re: [all] Should our gitignore files contain only build-related entries?

Hi, I usually only use what gibo [1] generates. I don’t put editor specific entries into .gitignore for my personal projects. This stuff should go into your personal gitignore. If developers don’t know about global gitignore we should educate them instead of promoting non-sense project setups.

Re: [lang] Appetite for new method StringUtils.toCamelCase(String str, char delimiter, boolean capitalizeFirstLetter)

Hi, > Am 01.06.2017 um 16:03 schrieb Rob Tompkins : > > Hello all, > > Folks at my day job have a method that takes in a space delimited String (or > arbitrarily delimited string for that matter), and returns a camel cased > string. Is there any reason that this shouldn’t

Re: [PARENT][PROPOSAL] Add Automatic-Module-Name MANIFEST entry

On 5 June 2017 at 09:35, Benedikt Ritter wrote: > Is there some documentation on how to check validity? I'm sure there is info in various places, but I've not seen a checklist. Off the top of my head: - all packages under a single super-package that is the module name -

Re: [TEXT]: No Github to commons-dev ML connectivity.

Hi, > Am 02.06.2017 um 21:44 schrieb Amey Jadiye : > > Hi, > > I have observed many mails from commons lang, fileupload, cli, compress > and many other modules where if someone opened PR or commented on it a copy > of activity comes to ML, but same doesn't happens for

Re: svn commit: r1797520 - /commons/proper/weaver/trunk/pom.xml

Hello Rob, > Am 03.06.2017 um 18:52 schrieb chtom...@apache.org: > > Author: chtompki > Date: Sat Jun 3 16:52:58 2017 > New Revision: 1797520 > > URL: http://svn.apache.org/viewvc?rev=1797520=rev > Log: > (chore) adding commons.module.name to pom > > Modified: >

Re: [PARENT][PROPOSAL] Add Automatic-Module-Name MANIFEST entry

Hello Stephen, > Am 24.05.2017 um 17:11 schrieb Stephen Colebourne : > > On 24 May 2017 at 15:55, Rob Tompkins wrote: >> We should simply add that entry, "commons.automatic-module-name," to every >> component pom’s properties section now, and then when

Re: [PARENT][PROPOSAL] Add Automatic-Module-Name MANIFEST entry

Hi, > Am 03.06.2017 um 18:54 schrieb Rob Tompkins : > > This should be done now with the entries being “commons.module.name” I’d recommend using dashes in the second part of the name, since my understanding of points is to declare name spaces. So I’d suggest to use