Re: [sanselan] how to build a release

2011-12-16 Thread Damjan Jovanovic
On Sat, Dec 17, 2011 at 1:35 AM, Gary Gregory wrote: > On Fri, Dec 16, 2011 at 5:54 PM, sebb wrote: > > > On 16 December 2011 20:49, Gary Gregory wrote: > > > On Fri, Dec 16, 2011 at 1:43 PM, sebb wrote: > > > > > >> On 16 December 2011 17:27, Simone Tripodi > > >> wrote: > > >> > AH yes, that

Re: [ognl] Old issues....

2011-12-16 Thread Christian Grobmeier
2011/12/16 Łukasz Lenart : > 2011/12/14 Christian Grobmeier : >> cool, thanks for the update. If you run out of time for some reason or >> see any other problems with the import, pls let me/us know. I gladly >> dedicate the cmd-c/cmd-v operations of the next days to ognl. > > I finished the work an

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

2011-12-16 Thread Gump
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-proxy-test has an issue affecting its community integration. This

[GUMP@vmgump]: Project commons-exec-test (in module apache-commons) failed

2011-12-16 Thread Gump
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-exec-test has an issue affecting its community integration. This i

Re: [sanselan] how to build a release

2011-12-16 Thread sebb
On 16 December 2011 23:35, Gary Gregory wrote: > On Fri, Dec 16, 2011 at 5:54 PM, sebb wrote: > >> On 16 December 2011 20:49, Gary Gregory wrote: >> > On Fri, Dec 16, 2011 at 1:43 PM, sebb wrote: >> > >> >> On 16 December 2011 17:27, Simone Tripodi >> >> wrote: >> >> > AH yes, that's because S

Re: [sanselan] how to build a release

2011-12-16 Thread Gary Gregory
On Fri, Dec 16, 2011 at 5:54 PM, sebb wrote: > On 16 December 2011 20:49, Gary Gregory wrote: > > On Fri, Dec 16, 2011 at 1:43 PM, sebb wrote: > > > >> On 16 December 2011 17:27, Simone Tripodi > >> wrote: > >> > AH yes, that's because Sanselan came from the Incubator and hasn't > >> > been up

Re: svn commit: r1215050 - in /commons/proper/jexl/tags/COMMONS_JEXL_2_1-RC3/src: main/java/org/apache/commons/jexl2/internal/MethodExecutor.java test/java/org/apache/commons/jexl2/IssuesTest.java

2011-12-16 Thread sebb
On 16 December 2011 13:33, sebb wrote: > On 16 December 2011 12:19, henrib wrote: >> I probably used manual editing, otherwise it would be properly reverted... >> If you have the svn command on top of your head to revert to the initial RC3 >> version, please send it; I'd rather not f...up again -

Re: [sanselan] how to build a release

2011-12-16 Thread sebb
On 16 December 2011 20:49, Gary Gregory wrote: > On Fri, Dec 16, 2011 at 1:43 PM, sebb wrote: > >> On 16 December 2011 17:27, Simone Tripodi >> wrote: >> > AH yes, that's because Sanselan came from the Incubator and hasn't >> > been updated yet :P >> >> Yes - that's good (as it happens). >> >> T

Re: [sanselan] how to build a release

2011-12-16 Thread Gary Gregory
On Fri, Dec 16, 2011 at 1:43 PM, sebb wrote: > On 16 December 2011 17:27, Simone Tripodi > wrote: > > AH yes, that's because Sanselan came from the Incubator and hasn't > > been updated yet :P > > Yes - that's good (as it happens). > > The previous (incubator) Maven release was under the groupId

Re: [sanselan] how to build a release

2011-12-16 Thread sebb
On 16 December 2011 18:43, sebb wrote: > On 16 December 2011 17:27, Simone Tripodi wrote: >> AH yes, that's because Sanselan came from the Incubator and hasn't >> been updated yet :P > > Yes - that's good (as it happens). > > The previous (incubator) Maven release was under the groupId > org.apac

Re: [sanselan] how to build a release

2011-12-16 Thread sebb
On 16 December 2011 17:27, Simone Tripodi wrote: > AH yes, that's because Sanselan came from the Incubator and hasn't > been updated yet :P Yes - that's good (as it happens). The previous (incubator) Maven release was under the groupId org.apache.sanselan, and the package was also o.a.sanselan

Re: [sanselan] how to build a release

2011-12-16 Thread Simone Tripodi
AH yes, that's because Sanselan came from the Incubator and hasn't been updated yet :P On Fri, Dec 16, 2011 at 6:04 PM, Gary Gregory wrote: > It looks like the first thing that should happen before a 1.0 is a > repackage under o.a.c. > > Gary http://people.apache.org/~simonetripodi/ http://simon

Re: [ognl] Old issues....

2011-12-16 Thread Łukasz Lenart
2011/12/14 Christian Grobmeier : > cool, thanks for the update. If you run out of time for some reason or > see any other problems with the import, pls let me/us know. I gladly > dedicate the cmd-c/cmd-v operations of the next days to ognl. I finished the work and I'm running copy of OpenSypmhony

Re: [sanselan] how to build a release

2011-12-16 Thread Gary Gregory
It looks like the first thing that should happen before a 1.0 is a repackage under o.a.c. Gary On Fri, Dec 16, 2011 at 11:56 AM, Gary Gregory wrote: > On Fri, Dec 16, 2011 at 11:28 AM, sebb wrote: > >> On 16 December 2011 15:07, Gary Gregory wrote: >> > Shouldn't we update the code to Java 5 a

Re: [sanselan] how to build a release

2011-12-16 Thread Gary Gregory
On Fri, Dec 16, 2011 at 11:28 AM, sebb wrote: > On 16 December 2011 15:07, Gary Gregory wrote: > > Shouldn't we update the code to Java 5 at least before a release? So > > that it looks and feels modern? The commons-io dep could be updated > > then too. Same for JUnit. > > Updating to Java 1.5 p

Re: [sanselan] how to build a release

2011-12-16 Thread sebb
On 16 December 2011 15:07, Gary Gregory wrote: > Shouldn't we update the code to Java 5 at least before a release? So > that it looks and feels modern? The commons-io dep could be updated > then too. Same for JUnit. Updating to Java 1.5 properly is a lot of work, but if there are people willing t

Re: [sanselan] how to build a release

2011-12-16 Thread Simone Tripodi
On Fri, Dec 16, 2011 at 4:07 PM, Gary Gregory wrote: > Shouldn't we update the code to Java 5 at least before a release? So > that it looks and feels modern? The commons-io dep could be updated > then too. Same for JUnit. > +1 > Gary > -Simo http://people.apache.org/~simonetripodi/ http://simo

Re: [sanselan] how to build a release

2011-12-16 Thread Gary Gregory
Shouldn't we update the code to Java 5 at least before a release? So that it looks and feels modern? The commons-io dep could be updated then too. Same for JUnit. Gary On Dec 16, 2011, at 5:30, sebb wrote: > On 16 December 2011 06:27, Damjan Jovanovic wrote: >> Thank you, this seems like what

Re: svn commit: r1215050 - in /commons/proper/jexl/tags/COMMONS_JEXL_2_1-RC3/src: main/java/org/apache/commons/jexl2/internal/MethodExecutor.java test/java/org/apache/commons/jexl2/IssuesTest.java

2011-12-16 Thread sebb
On 16 December 2011 12:19, henrib wrote: > I probably used manual editing, otherwise it would be properly reverted... > If you have the svn command on top of your head to revert to the initial RC3 > version, please send it; I'd rather not f...up again - even better, apply it > if you still can. :-

Re: svn commit: r1215050 - in /commons/proper/jexl/tags/COMMONS_JEXL_2_1-RC3/src: main/java/org/apache/commons/jexl2/internal/MethodExecutor.java test/java/org/apache/commons/jexl2/IssuesTest.java

2011-12-16 Thread henrib
I probably used manual editing, otherwise it would be properly reverted... If you have the svn command on top of your head to revert to the initial RC3 version, please send it; I'd rather not f...up again - even better, apply it if you still can. :-) Thanks PS: What about 2.1.1, do you or do I ?

Re: [math] OK to instanciate MathIllegalArgumentException directly?

2011-12-16 Thread Gilles Sadowski
Hello. > I'm still working on MATH-677, and would like to remove the > IllegalArgumentExceptions thrown if the length of the data set is not > a power of two. I was simply considering throwing > MathIllegalArgumentException, but this is discouraged in the Javadoc. > Can I break this rule, or shoul

Re: svn commit: r1215050 - in /commons/proper/jexl/tags/COMMONS_JEXL_2_1-RC3/src: main/java/org/apache/commons/jexl2/internal/MethodExecutor.java test/java/org/apache/commons/jexl2/IssuesTest.java

2011-12-16 Thread sebb
On 16 December 2011 07:09, wrote: > Author: henrib > Date: Fri Dec 16 07:08:59 2011 > New Revision: 1215050 > > URL: http://svn.apache.org/viewvc?rev=1215050&view=rev > Log: > Unfix for JEXL-124, not supposed to happen on RC3 tag! Did you revert by manual editting? Or using SVN commands? The ch

Re: [sanselan] how to build a release

2011-12-16 Thread sebb
On 16 December 2011 06:27, Damjan Jovanovic wrote: > Thank you, this seems like what I needed. It turns out gpg-agent has to be > used to sign. > > Unfortunately the Internet bandwidth required to upload all the files is > vast, so a Sanselan release is probably only going to happen in January. P

Re: svn commit: r1214986 - in /commons/proper/jexl/tags/COMMONS_JEXL_2_1-RC3/src: main/java/org/apache/commons/jexl2/internal/MethodExecutor.java test/java/org/apache/commons/jexl2/IssuesTest.java

2011-12-16 Thread sebb
On 16 December 2011 07:26, henrib wrote: > Should not commit that late... > Reverted RC3, applied fix on 2.0 branch. > Thanks for catching this! I always use http: rather than https: when checking out tags - avoids accidents. > -- > View this message in context: > http://apache-commons.680414.n