Re: Merged my first couple of patches from GitHub

On Thu, Feb 25, 2016 at 11:25 PM, Benedikt Ritter <brit...@apache.org> wrote: > 2016-02-26 6:20 GMT+01:00 Henri Yandell <flame...@gmail.com>: > > > AAarRRRrrrGgggghHHhhh > > > > That was painful. > > > > Have you read [1]? :o) >

Merged my first couple of patches from GitHub

AAarRRRrrrGgggghHHhhh That was painful. Hen

Re: [math] [POLL] new TLP name

Apache Math. On Tue, Feb 2, 2016 at 11:52 AM, Martin Grotle Soukup < martin.grotle.sou...@gmail.com> wrote: > I think Apache Math sounds most promising. > > Best regards > Martin Grotle Soukup > > 2016-02-01 18:06 GMT+01:00 Phil Steitz : > > > Please select your top choice

Re: [math] Name of the new TLP

Any reason why you're not going with Apache Math - math.apache.org? No one is going to wince if you have other language implementations in the same project, and if it needs to break up over time because there is Apache Math GroupTheory, Apache Math Fluid Dynamics etc etc; then more power to

Re: [VOTE] Form a separate TLP based on [math]

On Sat, Jan 16, 2016 at 7:18 AM, Phil Steitz wrote: > The discussion has thus far been generally favorable. I would like > therefore to put the proposal to split [math] out into a separate > TLP to a VOTE. Assuming a favorable vote, we can discuss how to go > about doing

Re: [math] TLP

+1 (non-binding). On Thu, Jan 14, 2016 at 1:59 PM, Siegfried Göschl < siegfried.goes...@it20one.com> wrote: > Hi folks, > > +1 for going TLP (non-binding) > > And the luck for Luc :-) > > Siegfried Goeschl > > > > - Ursprüngliche Mail - > Von: "Luc Maisonobe" > An:

Re: Proposed fluent string utils

My suggestion would be to add a link to teh Commons Lang website to Micha's repo and see how successful it is (i.e. if successful, I'd expect to see users contributing other Lang related fluent APIs to it). I'd suggest renaming to fluengLang :) On Mon, Nov 16, 2015 at 11:50 AM, Benedikt Ritter

Re: [VOTE] Accept Naomi

On Sat, Oct 31, 2015 at 2:49 PM, Phil Steitz wrote: > On 10/31/15 3:35 AM, Uwe Barthel wrote: > > Hi Siegfried, > > > > Thanks for your clarification. > > > > It's really commonly use to bypass the incubator for small projects to > become Apache Commons subproject status?

Re: Proposed Contribution to Apache Commons,

On Tue, Sep 29, 2015 at 5:42 PM, Phil Steitz wrote: > On 9/29/15 3:55 PM, Gary Gregory wrote: > > Norman, > > > > Hello and welcome to Apache Commons. > > > > It's not clear to me why Naomi is better than regular expressions. > Pointing > > to Javadocs is not the best way

Re: need some help

The currently active projects is a good question (and as I'm not that active myself, let's see which are active). When we were all using Subversion it was easier, but now some components are on Git and some Subversion. Looks like four are on Git (Math, Lang, Compress and SCXML). I would assume,

Re: [lang] running tests in eclipse

Try this one: https://issues.apache.org/jira/browse/LANG-1143 Sebb's already broken the back on it and I laid out the remaining work. If you've not hit codepoints before, they're quite an interesting area to dive into. You don't need to dive into it much, but reading up on them so you

Re: [lang] Differences in commons-lang (2.x) and commons-lang3 prevent TomEE project from migrating completely (Was: Re: [JCS] release?)

On Sat, Oct 18, 2014 at 2:44 PM, Phil Steitz phil.ste...@gmail.com wrote: On 10/18/14 2:03 PM, Paul Benedict wrote: You are not including duplicate artifacts, they are totally distinct. I think Romain's point is that classes that are not changed in the different versions are duplicated.

Re: [lang] Rationale for multiplying by one in Conversion?

+1 to remove. On Mon, Apr 21, 2014 at 1:42 PM, Duncan Jones djo...@apache.org wrote: Hi everyone, The Conversion class has numerous instances in which a value is multiplied by one (e.g. line 1054): shift = i * 1 + dstPos; I suspect this is a copy/paste issue, since other parts of the

Re: [lang] Problem with running tests

Note that checking out from trunks-proper should check out the same code. It's a way to check out all of the Commons component's trunks at the same time. Hen On Fri, Apr 4, 2014 at 9:36 AM, Benedikt Ritter benerit...@gmail.comwrote: Hello Svitana, you've checken out from the wrong location.

Re: [VOTE] Move Commons Betwixt to dormant

+1. On Thu, Mar 13, 2014 at 11:19 AM, Benedikt Ritter brit...@apache.orgwrote: My +1 for the record 2014-03-11 21:08 GMT+01:00 Benedikt Ritter brit...@apache.org: Hi all, as discussed, I'd like to propose to move Apache Commons Betwixt to dormant. Reasons: - no real activity

Re: [LANG] Towards 3.3

of with an ICLA. Benedikt 2014/1/27 Henri Yandell flame...@gmail.com Depends whose arguing probably :) Our license gives us a right to contributions under Apache 2.0 unless stated otherwise; the ICLA is playing safer. We can also simply take anything under a compatible license and include

Re: [LANG] Towards 3.3

Depends whose arguing probably :) Our license gives us a right to contributions under Apache 2.0 unless stated otherwise; the ICLA is playing safer. We can also simply take anything under a compatible license and include (with suitable licensing). I did that for a method from Spring. Hen On

Re: svn commit: r1560382 - /commons/proper/csv/trunk/src/main/java/org/apache/commons/csv/CSVPrinter.java

+1. Makes svn blame useless by creating a date in time when everything was touched. On Thu, Jan 23, 2014 at 10:07 AM, sebb seb...@gmail.com wrote: I think there is a big difference between creating a class with sorted methods, and retrospectively sorting methods in an existing class. That

Re: svn commit: r1560762 - /commons/proper/lang/trunk/src/test/java/org/apache/commons/lang3/StringUtilsTest.java

In case you didn't get an answer here: http://stackoverflow.com/questions/304383/how-do-i-edit-a-log-message-that-i-already-committed-in-subversion $svn propedit -r N --revprop svn:log URL $svn propset -r N --revprop svn:log new log message URL On Thu, Jan 23, 2014 at 9:17 AM, Benedikt Ritter

Re: [LANG] New class called StringAlgorithms?

On Mon, Jan 20, 2014 at 8:01 AM, Benedikt Ritter brit...@apache.org wrote: 2014/1/18 Oliver Heger oliver.he...@oliver-heger.de Am 18.01.2014 17:40, schrieb Emmanuel Bourg: Le 18/01/2014 16:04, Benedikt Ritter a écrit : About putting this into codec: I still don't think this is a

Re: [VOTE] Release Commons Lang 3.2.1 based on RC1

(non-binding) +1 from me :) Reviewed the diff between 3.2 and 3.2.1 tags. Source builds happily for me. Hen On Sun, Jan 5, 2014 at 10:26 AM, Benedikt Ritter brit...@apache.org wrote: Hi all, during the vote for Commons Lang 3.2, two issues were identified, namely: LANG-937: Fix missing

Re: [LANG] Next steps

On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com Better move quick on 3.2.1. Only bit I don't like about that is that it implies we shouldn't be committing anything that would lead us to want to have a 3.3

Re: [LANG] Snap-shot version in website header

/release of the code base. G Original message From: Benedikt Ritter brit...@apache.org Date:01/03/2014 08:12 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: Re: [LANG] Snap-shot version in website header 2014/1/3 Henri Yandell flame...@gmail.com

Re: [LANG] Next steps

On Sat, Jan 4, 2014 at 3:14 AM, Benedikt Ritter brit...@apache.org wrote: 2014/1/4 Henri Yandell flame...@gmail.com On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com I'm +1 for calendar

Re: [LANG] Next steps

On Sat, Jan 4, 2014 at 11:44 AM, Henri Yandell flame...@gmail.com wrote: On Sat, Jan 4, 2014 at 3:14 AM, Benedikt Ritter brit...@apache.orgwrote: 2014/1/4 Henri Yandell flame...@gmail.com On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen

Re: [LANG] Next steps

Also +1 to all. On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory garydgreg...@gmail.com wrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject:

Re: [LANG] Snap-shot version in website header

Yes we change the site between releases. The bigger question is why we have a version number on the website, it isn't versioned. Hen On Thu, Jan 2, 2014 at 6:45 AM, Duncan Jones dun...@wortharead.com wrote: Hi all, The top of the commons-lang web page reads: Last Published: 01 January

Re: [LANG] Next steps

:) Hen On Thu, Jan 2, 2014 at 8:56 PM, Henri Yandell flame...@gmail.com wrote: Also +1 to all. On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory garydgreg...@gmail.comwrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29

Re: [VOTE] Release Commons Lang 3.2 based on RC2

+1. On Sat, Dec 28, 2013 at 9:57 AM, Benedikt Ritter brit...@apache.org wrote: Hi all, I've fixed the issues, that were identified in RC1: - Release notes now make explicit that 3.2 at least requires Java 6.0 - Website now makes explicit that 3.2 at least requires Java 6.0 - MANIFEST now

Re: [OGNL] A new release

JIRA issue reopened btw as I noticed it was still resolved. On Wed, Dec 25, 2013 at 11:10 AM, Jason Pyeron jpye...@pdinc.us wrote: -Original Message- From: Benedikt Ritter Sent: Wednesday, December 25, 2013 11:53 You've set the issue to status resolved. That's propably the

Re: [ALL] Stack Overflow are offering free open source adverts - should we partake?

On Sat, Dec 7, 2013 at 12:43 AM, Benedikt Ritter benerit...@gmail.comwrote: Send from my mobile device Am 06.12.2013 um 18:11 schrieb sebb seb...@gmail.com: On 6 December 2013 14:11, Duncan Jones djo...@cantab.net wrote: On 6 December 2013 12:51, Benedikt Ritter benerit...@gmail.com

Re: javadocs

Here's an old thought - but why not centralize the javadoc? Instead of having components managing their release javadoc, instead make a central library in which the javadoc sites, then deep link to a components item within it. Then it's pretty easy to find an old release, pull the javadoc out and

Re: [all] Removing websites of dormant components

I think we should keep the lights on, but no more. So sites should exist to that level. What is the minimum needed on the site for a dormant project? Pointer to this list, explanation of what it is/was, pointer to old releases and to the location of the source history. I'm torn on javadoc; I

Re: ApacheCon Asia

A better question for commun...@apache.org. Hen On Tue, Nov 19, 2013 at 1:38 AM, Edward J. Yoon edwardy...@apache.orgwrote: Hi, I'm just curious, since 2006, ApacheCon was never held in Asia again. Is there any particular reason? Anybody can hold a conference? Thanks. -- Best Regards,

Re: Snapshot vs. release sites.

On Fri, Nov 8, 2013 at 4:24 AM, sebb seb...@gmail.com wrote: On 7 November 2013 17:45, Phil Steitz phil.ste...@gmail.com wrote: On 11/6/13 10:11 PM, Henri Yandell wrote: On Wed, Nov 6, 2013 at 7:53 AM, Gary Gregory garydgreg...@gmail.com wrote: Hi All: I find it unhelpful

Re: [LANG] Release 3.2?

the first RC. Benedikt Send from my mobile device Am 07.11.2013 um 07:15 schrieb Gary Gregory garydgreg...@gmail.com: Release early, release often :) Original message From: Henri Yandell flame...@gmail.com Date:11/07/2013 01:13 (GMT-05:00) To: Commons Developers

Applying GitHub pull requests

Apologies if this is obvious to all, but I figured I'd share as it took a moment to look it up and get the right answer out of the noise on StackOverflow :) A simple way to apply a GitHub pull request, say: https://github.com/apache/commons-lang/pull/11/ Download (wget etc)

Re: svn commit: r1535555 - in /commons/proper/lang/trunk/src: changes/changes.xml main/java/org/apache/commons/lang3/time/StopWatch.java test/java/org/apache/commons/lang3/time/StopWatchTest.java

On Fri, Oct 25, 2013 at 12:58 AM, Benedikt Ritter benerit...@gmail.comwrote: Hi Hen, 2013/10/24 bay...@apache.org Author: bayard Date: Thu Oct 24 21:23:40 2013 New Revision: 153 URL: http://svn.apache.org/r153 Log: Applying Sebb's patch from LANG-774 - adding isStarted,

Re: svn commit: r1535519 - /commons/proper/lang/trunk/src/changes/changes.xml

I removed the full stop/period on the end of the line. Thus it was modified. Bit weird that the diff made it -,+,+ rather than +,-,+ which would seem more natural. Hen On Fri, Oct 25, 2013 at 12:50 AM, Benedikt Ritter brit...@apache.orgwrote: Just a technical question: why was the row about

Re: [BCEL] Add link to 5.2 JavaDoc to site

Java doc isn't in the tar.gz for that version? On Friday, October 25, 2013, Benedikt Ritter wrote: 2013/10/25 Gary Gregory garydgreg...@gmail.com javascript:; On Fri, Oct 25, 2013 at 10:35 AM, Benedikt Ritter brit...@apache.orgjavascript:; wrote: 2013/10/25 Gary Gregory

Re: [LANG] Findbugs and CheckStyle

Noting that we've not stopped having Findbugs, Checkstyle and PMD notes from blocking a release in the past if we didn't agree with them. Checkstyle should get improved, but it's not a regression (ie: 3.2 would be no worse than 3.1). Hen On Wed, Oct 23, 2013 at 11:21 PM, Benedikt Ritter

Re: [maven build] Jira report?

On Tue, Oct 22, 2013 at 12:04 PM, Benedikt Ritter brit...@apache.orgwrote: 2013/10/22 sebb seb...@gmail.com On 22 October 2013 19:40, Henri Yandell flame...@gmail.com wrote: Anyone know what the point of the JIRA report is? It seems to be much like the changes report, but with less

Re: [maven build] Jira report?

. Humans = potential for errors; computers = less so ;) So I am not crazy about removing information for a given component unless the RN is of the historical nature. Gary On Wed, Oct 23, 2013 at 12:58 PM, Henri Yandell flame...@gmail.com wrote: On Tue, Oct 22, 2013 at 12:04 PM, Benedikt

Re: [lang] clirr violations

Check http://issues.apache.org/jira/browse/LANG-462 comments for the justification of the BC not being an issue. Hen On Wed, Oct 23, 2013 at 10:24 AM, Gary Gregory garydgreg...@gmail.comwrote: The current Clirr report shows errors. Do want to go to a 4.0 or fix the BC break and do a 3.2?

Re: svn commit: r1534380 - in /commons/proper/lang/trunk/src: main/java/org/apache/commons/lang3/NotImplementedException.java test/java/org/apache/commons/lang3/NotImplementedExceptionTest.java

On Tue, Oct 22, 2013 at 12:26 PM, Benedikt Ritter brit...@apache.orgwrote: Hi Hen, 2013/10/21 bay...@apache.org + * @author Apache Software Foundation This author tag looks strange. Did you add it by purpose? Removed :) Thanks for the catch; it was something we used to do in Commons

[maven build] Jira report?

Anyone know what the point of the JIRA report is? It seems to be much like the changes report, but with less active authorship and a confusing inclusion of resolved issues for different versions. I'm wondering why we include it. Hen

Re: svn commit: r1532011 - in /commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3: ArrayUtils.java ObjectUtils.java

On Mon, Oct 21, 2013 at 7:29 AM, sebb seb...@gmail.com wrote: On 21 October 2013 11:52, Benedikt Ritter benerit...@gmail.com wrote: Send from my mobile device Am 21.10.2013 um 03:46 schrieb sebb seb...@gmail.com: On 20 October 2013 15:03, Benedikt Ritter brit...@apache.org wrote:

Re: svn commit: r1532011 - in /commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3: ArrayUtils.java ObjectUtils.java

On Mon, Oct 21, 2013 at 12:28 PM, Henri Yandell flame...@gmail.com wrote: On Mon, Oct 21, 2013 at 7:29 AM, sebb seb...@gmail.com wrote: On 21 October 2013 11:52, Benedikt Ritter benerit...@gmail.com wrote: Send from my mobile device Am 21.10.2013 um 03:46 schrieb sebb seb

[lang] Issue focus

Thinking out loud - Here are the JIRA issues I think we should focus on: What's left in 3.2: https://issues.apache.org/jira/issues/?jql=project+%3D+LANG+AND+fixVersion+%3D+%223.2%22+AND+resolution+%3D+Unresolved The list of issues with patches that need reviewing:

Re: svn commit: r1532011 - in /commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3: ArrayUtils.java ObjectUtils.java

My tuppence: Lang 3 targets Java 6, but users can go upgrade to Java 7. So the deprecated warnings are actionable by changing your code to Java 7. Internal use - would this lead to warnings? As long as it isn't leading to warnings, updating internal is only a best practice and in this case

Re: [OT][LANG] Blog post about Validate vs. Guava Preconditions

Definitely jealous about the no apologies - for both Java versions and removing methods from the API without changing package name. On Fri, Oct 18, 2013 at 7:40 AM, Ted Dunning ted.dunn...@gmail.com wrote: In general, it is going to be very, very hard for Commons to go up against guava. The

Re: [LANG] Why do we have two checkstyle reports?

Thanks Thomas, that worked :) On Fri, Oct 18, 2013 at 8:18 AM, Thomas Neidhart thomas.neidh...@gmail.comwrote: Hi Benedikt, just add a reportSets definition to your checkstyle plugin, then the aggregate results will not be published: plugin groupIdorg.apache.maven.plugins/groupId

Re: [CHALLENGE] Move All of Commons to the Dormant

On Wed, Oct 16, 2013 at 11:14 PM, Jörg Schaible joerg.schai...@scalaris.com wrote: Henri Yandell wrote: My first thought was We should delete that page. :) Done at least for Release In Progress, last change 4 years ago. Funny enough it had a line for Collections 4.0 ;-) There's a lot

Re: [VOTE] Move Apache Commons to Git for SCM...

and have a beer, and enjoy. On 10/16/2013 11:56 PM, Henri Yandell wrote: There's no veto notion here - if we're abiding by the lowest denominator of the base Apache voting rules, vetoes are only for code votes. While this is to do with code, it's not code itself. I see it settled

[lang] LANG-781

Matt/Gary: Are we able to move onwards with this issue? https://issues.apache.org/jira/browse/LANG-781 You seemed in agreement. Are the ObjectUtils patches good to apply, and does the Validate patch need implementing? Should the validate part be split off as a separate issue? Hen

Re: [LANG] JIRA management

for it. we should also add a comment the the website so that people know where to start. 2013/10/15 Henri Yandell flame...@gmail.com One reason I like this, apart from the general visualization of the state of our todo group, is that it gives us a very nice way to point new contributors

[math][lang] LANG-912: Math.sum(int...)

Should this issue be in Math? https://issues.apache.org/jira/browse/LANG-912 Perhaps as ArithmeticUtils.addAndCheck(int...) ? Or should we be thinking of implementing on the Lang side? Hen

Re: [LANG] Deprecate time* package?

I'm +1 for that. On Wed, Oct 16, 2013 at 10:10 AM, Benedikt Ritter brit...@apache.orgwrote: Hi, Hen, you have expressed that you thing Java 8 will make the time package obsolete. Do we want to deprecate it? Benedikt -- http://people.apache.org/~britter/

Re: [CHALLENGE] Move All of Commons to the Dormant

My first thought was We should delete that page. :) On Wed, Oct 16, 2013 at 4:26 AM, Ted Dunning ted.dunn...@gmail.com wrote: Careful there. Hen might suggest making that list dormant. Sent from my iPhone On Oct 16, 2013, at 0:38, Jörg Schaible joerg.schai...@gmx.de wrote: BTW: We

Re: [CHALLENGE] Move All of Commons to the Dormant

On Wed, Oct 16, 2013 at 4:59 PM, sebb seb...@gmail.com wrote: On 16 October 2013 12:25, Christian Grobmeier grobme...@gmail.com wrote: If nobody is willing to put a component to dormant state, then the label doesn't make any sense. I would vote to remove the dormant state in general. If

Re: [math][lang] LANG-912: Math.sum(int...)

Thanks Gilles. I've moved it over. On Wed, Oct 16, 2013 at 2:24 AM, Gilles gil...@harfang.homelinux.orgwrote: On Wed, 16 Oct 2013 02:12:41 -0700, Henri Yandell wrote: Should this issue be in Math? https://issues.apache.org/**jira/browse/LANG-912https://issues.apache.org/jira/browse/LANG

Re: [CHALLENGE] Move All of Commons to the Dormant

On Tue, Oct 15, 2013 at 12:33 AM, Emmanuel Bourg ebo...@apache.org wrote: Le 15/10/2013 09:13, Henri Yandell a écrit : Related; here's the output of a 2006 script I've dusted off to show the number of commits and from who to each component in 2013: http://people.apache.org/~bayard

Re: svn commit: r1532031 - /commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3/BooleanUtils.java

On Mon, Oct 14, 2013 at 11:10 PM, Henri Yandell flame...@gmail.com wrote: I think we treat it as a bug and fix. The code is fine for the explained use of an array of length 2, but fails when you move to larger chains. Given the common meaning of the name, I think people would have noticed

[LANG] JIRA management

So the current management process in JIRA is a bit rusty, but is intended to be (as in I used to do it that way but no reason why anyone else should): New issue comes in (Version Unscheduled) We assign it to a future version. We use 3.2 for 'yes, soon' and 3.x for 'later'. It gets done with said

Re: [DISCUSS] Why is releasing such a pain and what can we do to make it easier?

On Mon, Oct 14, 2013 at 12:16 AM, Mark Thomas ma...@apache.org wrote: On 14/10/2013 02:55, Henri Yandell wrote: On Tuesday, October 8, 2013, Benedikt Ritter wrote: Hi, one of the points that seem to always come up once in a while is the process of releasing components. I've never

Re: [LANG] JIRA management

On Mon, Oct 14, 2013 at 1:19 AM, Emmanuel Bourg ebo...@apache.org wrote: Le 14/10/2013 08:06, Henri Yandell a écrit : What do others think? I quite like triaging the feature requests with a 'n.x' version and a '(n+1).0' version. The former indicates that the request can be implemented

Re: Jira is nuts

On Mon, Oct 14, 2013 at 1:04 AM, Emmanuel Bourg ebo...@apache.org wrote: Le 14/10/2013 02:48, Gary Gregory a écrit : One small step for man, one giant leap backward for mankind ;) Should we vote to migrate back to Bugzilla then ? ;) Stick a big banner on the Apache JIRA saying Wow, this

Re: [DISCUSS] Putting several unmaintained components to dormant

Wearing my old Attic fart hat - something is dead when there is no one left to turn the light out. Something is inactive when it couldn't pass a vote to keep the project alive (ie: 3 +1s). So that's one way to do this. Make a file in SVN. Put each component in it (include the sandbox perhaps).

Re: [DISCUSS] Putting several unmaintained components to dormant

to require. And then once we have the initial pruning done, how do we keep from backsliding into current state. That is what my 0) - 2) were referring to. Phil Benedikt 2013/10/14 Phil Steitz phil.ste...@gmail.com On 10/14/13 2:04 AM, Henri Yandell wrote: Wearing my old Attic fart

Re: [LANG] JIRA management

On Mon, Oct 14, 2013 at 8:56 AM, Benedikt Ritter brit...@apache.org wrote: Hi Hen, anything that makes working through the issues easier is good. But I think i don't understand your proposal completely. Do you want to create a new version that is called feature requests? That would feel like

Re: [LANG] JIRA management

didn't agree with will have been closed, and ones needing more in depth working out will be in Needs Investigation). It also gives us a group to go to when we're working out what cna go in 3.2 pre release; we look at the review needed group. Hen On Mon, Oct 14, 2013 at 5:04 PM, Henri Yandell

[CHALLENGE] Move All of Commons to the Dormant

I contend that all of the Commons components are inactive and should move to the Attic/Dormant. In line with Phil's recent suggestion that anyone can present a dormancy challenge at any time, I'm challenging all of Commons Proper. I've made a file in SVN:

Re: [LANG] Towards 3.2 and beyond

...) which does substitution in the message, while Objects only has requireNotNull(Object, String). Deprecating only Validate.notNull(T) would be strange, wouldn't it? Benedikt 2013/10/13 Henri Yandell flame...@gmail.com Website fixed :) On Sat, Oct 12, 2013 at 10:22 AM, Henri Yandell

Re: svn commit: r1532031 - /commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3/BooleanUtils.java

I think we treat it as a bug and fix. The code is fine for the explained use of an array of length 2, but fails when you move to larger chains. Given the common meaning of the name, I think people would have noticed if they'd needed xor to work for arrays 2 and it didn't. So a) I think we can fix

Re: [CHALLENGE] Move All of Commons to the Dormant

phil.ste...@gmail.com wrote: On 10/14/13 9:14 PM, Phil Steitz wrote: On 10/14/13 8:55 PM, Henri Yandell wrote: I contend that all of the Commons components are inactive and should move to the Attic/Dormant. In line with Phil's recent suggestion that anyone can present a dormancy

Re: [CHALLENGE] Move All of Commons to the Dormant

. On 10/14/2013 11:55 PM, Henri Yandell wrote: I contend that all of the Commons components are inactive and should move to the Attic/Dormant. In line with Phil's recent suggestion that anyone can present a dormancy challenge at any time, I'm challenging all of Commons Proper. I've made

Re: [LANG] Towards 3.2 and beyond

Website fixed :) On Sat, Oct 12, 2013 at 10:22 AM, Henri Yandell flame...@gmail.com wrote: I think this is the priority issue: https://issues.apache.org/jira/browse/LANG-894 If we can't fix and deploy our website, having new code is largely pointless :) I'm guessing we're on some

Re: Site Builds and Release Votes

On Sun, Oct 13, 2013 at 11:03 AM, Luc Maisonobe luc.maison...@free.frwrote: Le 13/10/2013 17:35, Stefan Bodewig a écrit : Hi all in the recent release vote for Compress Gary and I had very different opinions on the importance of the site build for release candidates. On 2013-10-13,

Re: [DISCUSS] Why is releasing such a pain and what can we do to make it easier?

On Tuesday, October 8, 2013, Benedikt Ritter wrote: Hi, one of the points that seem to always come up once in a while is the process of releasing components. I've never done it myself so I'm asking people who have done it: I find myself wondering why a release vote is anything more than:

Re: [DISCUSS] Why is releasing such a pain and what can we do to make it easier?

On Sun, Oct 13, 2013 at 7:09 PM, Ted Dunning ted.dunn...@gmail.com wrote: On Mon, Oct 14, 2013 at 2:55 AM, Henri Yandell flame...@gmail.com wrote: I propose release votes be simple revision based requests and involve no artifact churn :) Hen, This is a pretty good idea. But I still

Re: [DISCUSS] Why is releasing such a pain and what can we do to make it easier?

On Sun, Oct 13, 2013 at 9:12 PM, Phil Steitz phil.ste...@gmail.com wrote: Could be I am misunderstanding the proposal. Do you mean a) RM is not obligated to do anything but tag a release and create tarballs or b) RM should just be trusted to do the right thing in getting stuff published

[LANG] Git pull requests

These are all sitting in our pull request queue: https://github.com/apache/commons-lang/pulls?direction=descpage=1sort=createdstate=open Not all are open, I know #1 is in the code but I don't know how to close the requests.

Re: [LANG] Towards 3.2 and beyond

+1 to Java 7, though if that only means a few methods should be removed I'd go with deprecating with a note they'll be removed in Lang 4.0. We should deprecate the time package warning that it will be replaced with a new package based on Java 8's new API in Lang 4.0 :) I'm assuming 4.0 will be

Re: [LANG] Towards 3.2 and beyond

components if Lang hasn't been fixed. Hen On Sat, Oct 12, 2013 at 10:17 AM, Henri Yandell flame...@gmail.com wrote: +1 to Java 7, though if that only means a few methods should be removed I'd go with deprecating with a note they'll be removed in Lang 4.0. We should deprecate the time package

Re: [DISCUSS] Creating Project for Release Process Testing...

+1 from me for anything that makes the release process sane. I'd be committing again if preparing a release was simple enough. As it is, I don't have the blocks of time needed to push out a release and committing to projects with no apparent release manager becomes an exercise in futility. Hen

Re: [DISCUSS] Moving to Git...

On Tue, Oct 8, 2013 at 12:10 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Never said the opposite but git or svn is not a questioin IMO, both are simple and usable today. I'm more attracted by features than the infra around a project. For me commons looks like a big sandbox where rules

Re: Apache Commons IRC Channel...

Plus the IRC channel is the only place you'll get to hear Commons history, Matt's music preference for 7th century heretical works and Emmanuel's business plan for IRC log blackmail. On Thu, Oct 10, 2013 at 9:15 AM, James Carman ja...@carmanconsulting.comwrote: As a reminder, we do have an IRC

Re: svn commit: r1519292 - in /commons/proper/lang/trunk: .gitignore pom.xml src/changes/changes.xml

It'd be hard to argue it's an expressive work imo, thus even with a header there would be nothing licensable. Hen On Sun, Sep 1, 2013 at 10:09 AM, Benedikt Ritter brit...@apache.org wrote: Does the .gitignore file need an AL header? -- Forwarded message -- From:

Re: Lang: ObjectUtils

I don't see any value having the first two methods - replacing the '==' sign is a bit too far in the 'provide simple methods' direction I think :) I think the third method is already in Lang as: ArrayUtils.contains(array, null); Having a containsNull is semantically nice, but I'm not sure

[LANG] Release Manager?

Anyone available to volunteer to release Lang? I'd love to see releases happening, but I don't have the free time myself :( I tend to have an hour available in the evening when the kids are asleep and that's tough to fit release management into. Hen

Re: [LANG] Release Manager?

haven't deemed crucial. Hen On Wed, May 1, 2013 at 6:15 AM, Gary Gregory garydgreg...@gmail.com wrote: I just went through the process for Codec so it painfully fresh in my mind... Give me an idea of when you'd like to see that happen. Gary On May 1, 2013, at 3:16, Henri Yandell flame

Re: [LANG] LANG-884 - OK to commit patch?

+1 to committing. On Mon, Apr 29, 2013 at 2:06 AM, sebb seb...@gmail.com wrote: https://issues.apache.org/jira/browse/LANG-884 has a patch to simplify FastDateFormat which I would like to apply. OK?

Re: Bad link in the javadocs

I'm not sure if metacpan is fine, but it has a working link for the package: https://metacpan.org/source/MSCHWERN/Text-Metaphone-1.96/ Hen On Mon, Apr 29, 2013 at 3:42 AM, Gary Gregory garydgreg...@gmail.comwrote: Hi Ron, Thank you for the report. Can you create a JIRA for this please? Do

Re: [collections] beta release - howto

Is less attention paid to the API for an alpha/beta? Hen On Sat, Apr 27, 2013 at 10:16 AM, Jochen Wiedmann jochen.wiedm...@gmail.com wrote: There is nothing special. Even with alpha, or beta as part of the version number, it is technically an ASF release, and therefore subject to the full

Re: [jira] [Updated] (CODEC-166) Base64 could be faster

On Sun, Apr 28, 2013 at 12:50 PM, Emmanuel Bourg ebo...@apache.org wrote: Le 31/01/2013 00:35, sebb a écrit : The Fix version should only be added when the issue has been fixed, and should indicate the release in which the fix is available Just noticed this message, the 'Fix version' field

Re: Staging site?

Thanks :) Did you mean a different url for your #2 below? That seems to be the url i'm after (the shared directory), but you linked to a page on the Commons site. Hen On Wed, Apr 24, 2013 at 3:41 AM, sebb seb...@gmail.com wrote: On 24 April 2013 05:28, Henri Yandell flame...@gmail.com wrote

Re: Staging site?

On Wed, Apr 24, 2013 at 10:38 AM, sebb seb...@gmail.com wrote: On 24 April 2013 17:53, Henri Yandell flame...@gmail.com wrote: Thanks :) Did you mean a different url for your #2 below? No. That seems to be the url i'm after (the shared directory), but you linked to a page

Staging site?

Looking at the site building docs, I could see how to modify the site (install a CMS plugin or just modify SVN and test locally, I went with the latter). My commit was then built by the buildbot. Where is the staging site to look at the buildbot output so I can then be happy pressing Publish? I

Re: Staging site?

So if you're using the SVN approach, you check locally, then commit and go hit publish on the CMS? Hen On Tue, Apr 23, 2013 at 11:50 AM, sebb seb...@gmail.com wrote: On 23 April 2013 19:25, Henri Yandell flame...@gmail.com wrote: Looking at the site building docs, I could see how to modify

Re: [io] readying release?

On Mon, Apr 22, 2013 at 2:33 AM, sebb seb...@gmail.com wrote: On 22 April 2013 03:41, Henri Yandell flame...@gmail.com wrote: On Sun, Apr 21, 2013 at 5:27 AM, sebb seb...@gmail.com wrote: On 21 April 2013 05:44, Henri Yandell flame...@gmail.com wrote: Proposed fix: https

  1   2   3   4   5   6   7   8   9   10   >