Re: svn commit: r1494980 - in /commons: proper/commons-gpg-plugin/ sandbox/commons-gpg-plugin/

2013/6/20 Simone Tripodi > On Thu, Jun 20, 2013 at 4:06 PM, sebb wrote: > > On 20 June 2013 14:48, Simone Tripodi wrote: > >> Don't you think it would worth at least announcing it, before moving a > >> component from sandbox to proper? > > > > I did, yesterday. > > > > So, to move Graph from sa

Re: [CHAIN] Thoughts about o.a.c.chain2.Chain, o.a.c.chain2.Command and the base classes

2013/6/21 Simone Tripodi > Thanks Jonas, > > would you submit a patch for that? TIA! > > -Simo > > http://people.apache.org/~simonetripodi/ > http://twitter.com/simonetripodi > > > On Thu, Jun 20, 2013 at 11:09 PM, Jonas Sprenger > wrote: > > Hi guys, > > > > so we talk about an enum 'PROCESSIN

Re: [CSV] remaining issues before 1.0

Hi Gary, nice to see some activity in CSV again. We were talking about reverting CSVFormat back to the old API that does not use the builder pattern, see CSV-99[1]. We still have 18 unresolved issues. I think we should go through all those issues and decide if we want to have them in 1.0. Regardi

Re: [CHAIN] Thoughts about o.a.c.chain2.Chain, o.a.c.chain2.Command and the base classes

Thanks Jonas, would you submit a patch for that? TIA! -Simo http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Thu, Jun 20, 2013 at 11:09 PM, Jonas Sprenger wrote: > Hi guys, > > so we talk about an enum 'PROCESSING' providing at least 3 states? > > - CONTINUE > - C

Re: [CSV] remaining issues before 1.0

[oops, send previous msg too soon] FIndBugs reports: Immediate dereference of the result of readLine() in org.apache.commons.csv.CSVLexer.nextToken(Token) at line 89. Which I addressed in SVN but wanted to check with the ML just in case... Gary On Thu, Jun 20, 2013 at 10:28 AM, Gary Gregory

Re: [CSV] remaining issues before 1.0

Thoughts on this FindBugs issue: On Thu, Jun 20, 2013 at 10:28 AM, Gary Gregory wrote: > So... what are the remaining issues before 1.0? > > Are we happy with the current state of the API? Builder and all? > > Gary > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence

Re: [ALL] Proposed tarball staging process

On 20 June 2013 22:22, Gary Gregory wrote: > Looks good. I would say use the plural for both: > > https://dist.apache.org/repos/dist/dev/commons/commons-net-3.3-RC1[/binaries|/sources] That is not the ASF con

Re: [ALL] Proposed tarball staging process

Looks good. I would say use the plural for both: https://dist.apache.org/repos/dist/dev/commons/commons-net-3.3-RC1[/binaries|/sources] Gary On Thu, Jun 20, 2013 at 2:53 PM, sebb wrote: > The current tarb

Re: [CHAIN] Thoughts about o.a.c.chain2.Chain, o.a.c.chain2.Command and the base classes

Hi guys, so we talk about an enum 'PROCESSING' providing at least 3 states? - CONTINUE - COMPLETE - ABORTED Ticket CHAIN-98 has been created to cover this task. regards, Jonas 2013/6/20 Simone Tripodi > Hallo Bene, > > > * JavaDoc of Command

Re: [ALL] Proposed tarball staging process

+1 http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Thu, Jun 20, 2013 at 8:53 PM, sebb wrote: > The current tarball (*) staging process uses Nexus, which works well > for Maven jars and is OK as a means of staging tarballs for voting. > > However: once the vote succe

[VOTE][LAZY] Release Commons Parent 31 from RC2

This is a VOTE to release Commons Parent 31-RC2 This VOTE by LAZY-CONSENSUS is open for at least 72 hours It will finish no earlier than June 23 at 20:00 GMT. The main changes in this release are: - dropped unused 'rc' profile - fixed the maven.compile[r] names - updated some plugins and the R

[ALL] Proposed tarball staging process

The current tarball (*) staging process uses Nexus, which works well for Maven jars and is OK as a means of staging tarballs for voting. However: once the vote succeeds, the tarballs need to be extracted and pushed to the dist/release repo. This is tricky and error-prone; it's possible to delete a

Re: [lang]

Hi Thomas, A few points: - you correctly prefixed your email [lang], but it would have been nice to have a bit more detail in the subject - enhancement requests and patches should be handled through the ASF JIRA instance - java.util.Arrays.asList() is the typically recognized way to create a l

Re: [lang]

Hello Thomas, how about java.util.Arrays.asList(T...)? Regards, Benedikt 2013/6/20 Thomas Lionel SMETS (prof) > Hello, > I have been looking for a method allowing me to convert a String[] into a > List. > As I could not find it on ArrayUtils, here is a small piece of code I > wrote : > >

[lang]

Hello, I have been looking for a method allowing me to convert a String[] into a List. As I could not find it on ArrayUtils, here is a small piece of code I wrote : /** * Converts a String[] into a List. * @param array the String[] to convert. * @return null if the reference pro

[CSV] remaining issues before 1.0

So... what are the remaining issues before 1.0? Are we happy with the current state of the API? Builder and all? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition

Re: svn commit: r1494980 - in /commons: proper/commons-gpg-plugin/ sandbox/commons-gpg-plugin/

On Thu, Jun 20, 2013 at 4:06 PM, sebb wrote: > On 20 June 2013 14:48, Simone Tripodi wrote: >> Don't you think it would worth at least announcing it, before moving a >> component from sandbox to proper? > > I did, yesterday. > So, to move Graph from sandbox to proper is enough I announce it in t

[ALL] Site for multiple versions of a component

Is there any thought on easing managing a site for multiple versions of a component. Right now, for some components, we have >1 Javadoc site. It would be nice to at least automate that. But why not have the whole site? https://commons.apache.org/proper/commons-lang/2.6 https://commons.apache.org/p

Re: svn commit: r1494980 - in /commons: proper/commons-gpg-plugin/ sandbox/commons-gpg-plugin/

On 20 June 2013 14:48, Simone Tripodi wrote: > Don't you think it would worth at least announcing it, before moving a > component from sandbox to proper? I did, yesterday. > http://people.apache.org/~simonetripodi/ > http://twitter.com/simonetripodi > > > On Thu, Jun 20, 2013 at 3:26 PM, wrote

Re: Commons plugins

On 20 June 2013 14:43, Gary Gregory wrote: > Is there any thought on easing managing a site for multiple versions of a > component. Please start a new thread for this. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

Re: svn commit: r1494980 - in /commons: proper/commons-gpg-plugin/ sandbox/commons-gpg-plugin/

Don't you think it would worth at least announcing it, before moving a component from sandbox to proper? http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Thu, Jun 20, 2013 at 3:26 PM, wrote: > Author: sebb > Date: Thu Jun 20 13:26:52 2013 > New Revision: 1494980 > >

Re: Commons plugins

Is there any thought on easing managing a site for multiple versions of a component. Right now, for some components, we have >1 Javadoc site. It would be nice to at least automate that. But why not have the whole site? https://commons.apache.org/proper/commons-lang/2.6 https://commons.apache.org/p

Re: [CHAIN] Thoughts about o.a.c.chain2.Chain, o.a.c.chain2.Command and the base classes

Hallo Bene, > * JavaDoc of Command says that commands have to be designed in a > thread-safe manner, yet all the base implementations are not thread safe! I > have created CHAIN-96 [1] for this, because this definitely has to be fixed > before 2.0 +1 > * The same is true for o.a.c.chain2.Chain

[CHAIN] Thoughts about o.a.c.chain2.Chain, o.a.c.chain2.Command and the base classes

Hi guys, I had a look at the command interface and it's base classes yesterday, and I think there is some work to do :) Here are the points I found: * JavaDoc of Command says that commands have to be designed in a thread-safe manner, yet all the base implementations are not thread safe! I have c