Luc Maisonobe wrote:
Luc Maisonobe a écrit :
Luc Maisonobe a écrit :
Phil Steitz a écrit :
Looks like we are - at last - ready to cut 2.0. All that remains is
1) resolve MATH-260 and MATH-261 (which I am +1 as marking fixed, based
on Luc's last changes)
+1
IMO its confusing that the NET_1_5_0_RC3 tag was created from the
first incorrectly tagged NET_2_1_RC1 (especially since that original
tag has been removed and re-created). Better IMO to re-tag properly a
RC4 from trunk
http://svn.apache.org/viewvc?view=rev&revision=796050
Niall
On Tue, Jul 21,
On Mon, Jul 20, 2009 at 12:24 PM, Stephen
Colebourne wrote:
> Henri Yandell wrote:
2) NullArgumentException
>>
>> How about putting in the backcompat?
>
> I would be fine with all four going in the backcompat.
Agreed. I've gone ahead and done that.
Hen
-
Hi folks
Fix release for the 2.0 branch.
Binaries/sources etc: http://people.apache.org/~rwinston/commons-net-2.1-RC1/
Tag: http://svn.apache.org/viewvc/commons/proper/net/tags/NET_2_1_RC1/
Fixes:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310487&fixfor=1231300
Hi folks
Been kicking around for a while:
Tag: http://svn.apache.org/viewvc/commons/proper/net/tags/NET_1_5_0_RC3/
Binaries/sources etc: http://people.apache.org/~rwinston/commons-net-1.5.0-RC3/
+1
+0
-0
-1
Thanks
--Rory
-
T
Luc Maisonobe a écrit :
> Luc Maisonobe a écrit :
>> Phil Steitz a écrit :
>>> Looks like we are - at last - ready to cut 2.0. All that remains is
>>>
>>> 1) resolve MATH-260 and MATH-261 (which I am +1 as marking fixed, based
>>> on Luc's last changes)
>> +1
>>
>>> 2) push remaining unschedule
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-jelly-tags-jaxme has an issue affecting its community
integration
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-jelly-tags-fmt-test has an issue affecting its community
integrat
Henri Yandell wrote:
2) NullArgumentException
How about putting in the backcompat?
I would be fine with all four going in the backcompat.
Stephen
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional c
I think NullArgumentException should be deprecated and removed. It is
becoming a best practice to use NPE for null arguments. Joshua Bloch
has produced two books containing such advice, and Google Collections
has gone this way too. By the way, it's because the JDK has set this
precedent.
Paul
On
Hi Stephen :)
On Sun, Jul 19, 2009 at 11:35 AM, Stephen
Colebourne wrote:
> Henri Yandell wrote:
>>
>> 1) All the exceptions are in lang.* rather than lang.exception.*. Now
>> that the subpackage is pretty empty, it's tempting to move the
>> exceptions themselves down there. Given that it's going
I can't RM (not a committer) but I will help out with codec-1.4.
yours,
Julius
On Sat, Jul 18, 2009 at 5:22 PM, Henri Yandell wrote:
> *nominates Gary* :)
>
> aka... not me. I'm still hoping someone else can RM Collections so I
> can stay focused on Lang and Taglibs RMing.
>
> On Fri, Jul 17, 2
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-jelly-tags-jaxme has an issue affecting its community
integration
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-jelly-tags-fmt-test has an issue affecting its community
integrat
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-configuration-test has an issue affecting its community
integrati
15 matches
Mail list logo