Re: [CANCEL][VOTE] Release Apache Commons Lang 3.6 based on RC2

When I build with the IBM JDK 8 that IBM includes with some Eclipse version I have laying around, I indeed get: java (2) org.apache.commons.lang3.time.FastDateParser_TimeZoneStrategyTest testLang1219(org.apache.commons.lang3.time.FastDateParser_TimeZoneStrategyTest) java.text.ParseException: Unpar

[LANG] Unsafe use of varargs (LANG-1295/1296)

Hi everyone, I would welcome some comments on LANG-1295 [1] and LANG-1296 [2], which I raised about unsafe use of varargs in ArrayUtils.toArray(T... items) and ArrayUtils.addAll(T[] array1, T... array2). Should we deprecate these methods (to be removed in 4.0), since they can cause a ClassCast

Re: [text] Please add your release data for 'commons'

> On May 23, 2017, at 7:18 PM, Benedikt Ritter wrote: > > >> Am 23.05.2017 um 09:07 schrieb Rob Tompkins : >> >> Could a PMC member perform this task for me? > > Done > Thanks. >> >> Cheers, >> -Rob >> >>> On May 23, 2017, at 8:59 AM, Apache Reporter Service >>> wrote: >>> >>> Hi, >>

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

Hi, > Am 22.05.2017 um 09:19 schrieb sebb : > > On 22 May 2017 at 13:14, Rob Tompkins > wrote: >> >>> On May 22, 2017, at 8:10 AM, Stephen Colebourne >>> wrote: >>> >>> On 22 May 2017 at 12:51, Rob Tompkins wrote: You could, in the parent, declare in the prop

[CANCEL][VOTE] Release Apache Commons Lang 3.6 based on RC2

Hello, I’m canceling this vote because: - mvn site does not work from the src distribution - test failures on IBM JDK (where else…) I don’t know when I have the time to work an this. Any help is highly appreciated. Regards, Benedikt > Am 19.05.2017 um 16:52 schrieb Benedikt Ritter : > > Hell

Re: [TEXT] Proposal for StrLookup API (TEXT-80)

Hello, > Am 22.05.2017 um 15:02 schrieb Kapil Neurgaonkar : > > Hello Benedikt, > > Thanks for the warm welcome! > >> On Mon, May 22, 2017 at 4:24 AM, Benedikt Ritter > > wrote: >> Hello Kapil, >> >>> Am 21.05.2017 um 16:26 schrieb Kapil Neurgaonkar >>

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

Hello Gilles, > Am 23.05.2017 um 06:46 schrieb Gilles : > > Hi Benedikt. > > On Sun, 21 May 2017 19:40:28 -0400, Benedikt Ritter wrote: >> Hi, >> >> at this year’s ApacheCON we had some nice presentations. I’d like to >> share the video recordings with you (in order they were held at the >> eve

Re: [text] Please add your release data for 'commons'

> Am 23.05.2017 um 09:07 schrieb Rob Tompkins : > > Could a PMC member perform this task for me? Done > > Cheers, > -Rob > >> On May 23, 2017, at 8:59 AM, Apache Reporter Service >> wrote: >> >> Hi, >> This is an automated email from reporter.apache.org. >> I see that you just pushed somet

Re: [LANG] Thoughts about Lang 4.0

Why does every discussion at commons become a discussion about jar hell? > Am 23.05.2017 um 12:17 schrieb sebb : > > On 23 May 2017 at 16:42, Stephen Colebourne > wrote: >> On 23 May 2017 at 16:07, sebb mailto:seb...@gmail.com>> >> wrote: >>> Huh? >>> >>> The whole

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 16:42, Stephen Colebourne wrote: > On 23 May 2017 at 16:07, sebb wrote: >> Huh? >> >> The whole point of changing the package name and Maven coords is to >> allow mutually incompatible jars to coexist peacefully on a single >> classpath. > > All you are doing in replacing one ki

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 16:07, sebb wrote: > Huh? > > The whole point of changing the package name and Maven coords is to > allow mutually incompatible jars to coexist peacefully on a single > classpath. All you are doing in replacing one kind of jar hell with another. Removing these methods means tha

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 16:22, Matt Sicker wrote: > Tying versions of commons-lang to releases of Java itself makes a bit of > sense to me, but then I do foresee projects containing like 5 different > versions of commons-lang in the future which is somewhat annoying. If the version of Lang is tied to J

Re: [LANG] Thoughts about Lang 4.0

Tying versions of commons-lang to releases of Java itself makes a bit of sense to me, but then I do foresee projects containing like 5 different versions of commons-lang in the future which is somewhat annoying. On 23 May 2017 at 10:07, sebb wrote: > On 23 May 2017 at 12:18, Stephen Colebourne

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 12:18, Stephen Colebourne wrote: > On 23 May 2017 at 11:54, sebb wrote: >>> Fixing it properly requires a major release, which implies that Lang >>> 4.0 is still Java 1.7 and should use the `org.apache.commons.lang3` >>> package name. >> >> I think that depends on whether the AP

Re: [LANG] Thoughts about Lang 4.0

On Tue, 23 May 2017 15:33:39 +0200, Jochen Wiedmann wrote: On Tue, May 23, 2017 at 12:19 PM, Gilles wrote: Can you be explicit with what counts as "noise"? Lets start with the number of threads, shall we? Or the number of "What depends on what" discussions? Or questions like "Which belongs

Re: [LANG] Thoughts about Lang 4.0

On Tue, May 23, 2017 at 12:19 PM, Gilles wrote: > Can you be explicit with what counts as "noise"? Lets start with the number of threads, shall we? Or the number of "What depends on what" discussions? Or questions like "Which belongs to what?" (Feel free to suggest another measure.) Jochen -

Fw: [text] Please add your release data for 'commons'

Could a PMC member perform this task for me? Cheers, -Rob > On May 23, 2017, at 8:59 AM, Apache Reporter Service > wrote: > > Hi, > This is an automated email from reporter.apache.org. > I see that you just pushed something to our release repository for the > 'commons' project > in the follow

Re: [LANG] Thoughts about Lang 4.0

I think +0 for #1, +1 for #2, and +1 for (#4 or #5). -1 for #3 (though +1 for a 3.7 deprecating these methods). For 4.0, I wonder if we could find a replacement for the property listeners from java.beans, or might be simpler just remove the property listeners, and have a simple interface for sp

[RESULT][VOTE] Release Commons Text 1.1 based on RC1

The vote passes with the following votes (in order of appearance): Amey Jadiye: +1 (non-binding) Bruno P. Kinoshita: +1 Benedikt Ritter: +1 Jörg Schaible: +1 Gary Gregory: +1 Rob Tompkins: +1 (non-binding) I will proceed with publishing the release candidate. Many thanks to all of those that help

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 11:54, sebb wrote: >> Fixing it properly requires a major release, which implies that Lang >> 4.0 is still Java 1.7 and should use the `org.apache.commons.lang3` >> package name. > > I think that depends on whether the API is backwards-compatible or not. > > If it *is* backwards-

Re: [IMAGING] Why don't we just release it?

On 23 May 2017 at 09:59, Emmanuel Bourg wrote: > Le 18/05/2017 à 18:54, sebb a écrit : >> I think the release should be marked as ALPHA. >> This is because: >> - there are many unresolved issues >> - it's highly likely that the next release will break compatibility > > +1 for an alpha release, ide

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 11:05, Stephen Colebourne wrote: > On 22 May 2017 at 00:56, Benedikt Ritter wrote: >> I think the time has come to start thinking about Lang 4.0. > > As I outlined in another thread, Lang 3.5 uses PropertyChangeListener, > which in module terms pulls in the whole of Swing and AW

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

Hi Benedikt. On Sun, 21 May 2017 19:40:28 -0400, Benedikt Ritter wrote: Hi, at this year’s ApacheCON we had some nice presentations. I’d like to share the video recordings with you (in order they were held at the event) Apache Commons - State of the Union by myself: https://www.youtube.com/wa

Re: [text] Deprecate CsvTranslators

Le 23/05/2017 à 01:06, Gary Gregory a écrit : > I wonder if we should deprecate CsvTranslators in favor of Commons CSV. I > wish I had noticed CsvTranslators eariler :-( +1 Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr

Re: [LANG] Thoughts about Lang 4.0

On Tue, 23 May 2017 11:13:21 +0200, Jochen Wiedmann wrote: On Mon, May 22, 2017 at 1:47 PM, Rob Tompkins wrote: - commons-system: a library focused on working with system properties and detection of the operation system, system’s architecture and Java version - commons-concurrent: a library

Re: [lang] Java 9 module investigations

Le 23/05/2017 à 00:52, Stephen Colebourne a écrit : > One final option is to declare an optional dependency on java.desktop, > such that the AbstractCircuitBreaker will fail to load unless the > end-user manually chooses to add java.desktop. I don't like it, but it > may be a compromise for compat

Re: [LANG] Thoughts about Lang 4.0

On 22 May 2017 at 00:56, Benedikt Ritter wrote: > I think the time has come to start thinking about Lang 4.0. As I outlined in another thread, Lang 3.5 uses PropertyChangeListener, which in module terms pulls in the whole of Swing and AWT. For a library like [lang] that is a bad thing and should

Re: [LANG] Thoughts about Lang 4.0

Le 23/05/2017 à 11:13, Jochen Wiedmann a écrit : > IMO, c-lang is running well, as it is. +1 Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.

Re: [LANG] Thoughts about Lang 4.0

On 23 May 2017 at 10:13, Jochen Wiedmann wrote: > I am -0 to -1 regarding the introduction of new components. I'd rather > see us redefine the purpose of commons-lang. The experience of > commons-math has demonstrated, IMO, that such new components will most > likely increase the noise without an

Re: [LANG] Thoughts about Lang 4.0

On Mon, May 22, 2017 at 1:47 PM, Rob Tompkins wrote: >> - commons-system: a library focused on working with system properties and >> detection of the operation system, system’s architecture and Java version >> - commons-concurrent: a library providing additional abstractions and >> implementati

Re: [IMAGING] Why don't we just release it?

Le 18/05/2017 à 18:54, sebb a écrit : > I think the release should be marked as ALPHA. > This is because: > - there are many unresolved issues > - it's highly likely that the next release will break compatibility +1 for an alpha release, ideally with its dedicated namespace to avoid conflicts with

Re: [text] Deprecate CsvTranslators

Seems reasonable to me as well, should deprecate in text 1.2 release and code should be move to Commons CSV , I think complete removal should go in Text 2.0 , whenever it will be. Regards, Amey On Tue, May 23, 2017, 4:41 AM Rob Tompkins wrote: > > > > On May 22, 2017, at 7:06 PM, Gary Gregory