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-scxml-test has an issue affecting its community integration.
This
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-sql has an issue affecting its community integration.
T
Hello.
I'm also feeling tired of those issues. I must point out that this seems so
complicated _because_ we depart from best practices (as finely described in
e.g. "Effective Java").
Whatever seems a help (and probably is sometimes) in one direction leads to
inconsistencies in another, like in thi
Hi,
2012/9/13 Gilles Sadowski :
> Hello.
>
> I'm also feeling tired of those issues. I must point out that this seems so
> complicated _because_ we depart from best practices (as finely described in
> e.g. "Effective Java").
> Whatever seems a help (and probably is sometimes) in one direction lead
On Thu, Sep 13, 2012 at 12:04:52PM +0200, Sébastien Brisard wrote:
> Hi,
>
> 2012/9/13 Gilles Sadowski :
> > Hello.
> >
> > I'm also feeling tired of those issues. I must point out that this seems so
> > complicated _because_ we depart from best practices (as finely described in
> > e.g. "Effectiv
Hi,
2012/9/13 Gilles Sadowski :
> On Thu, Sep 13, 2012 at 12:04:52PM +0200, Sébastien Brisard wrote:
>> Hi,
>>
>> 2012/9/13 Gilles Sadowski :
>> > Hello.
>> >
>> > I'm also feeling tired of those issues. I must point out that this seems so
>> > complicated _because_ we depart from best practices (
On Wed, Sep 12, 2012 at 06:04:51PM +0200, Luc Maisonobe wrote:
> Le 12/09/2012 16:32, Gilles Sadowski a écrit :
> >
> > I think that "silly classes" should not be allowed in CM!
>
> As all I am able to do is silly work, [...]
^^
Didn't you mean "silly walk"? 8-
Hi Sébastien.
> > [...]
> Right, this means I must revert (again!) my changes... We will get
> there, eventually.
Knowing that it was a huge effort (to get everything right), I had set 3.2
as the target for MATH-854.
IMHO, there is no urgency to fix it in the coming days. After all, there is
noth
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
On Thu, Sep 13, 2012 at 01:10:41AM +0200, Gilles Sadowski wrote:
> Hello.
>
> [For those who don't wish to read the whole post, please at least go towards
> the end and indicate your preferred option. Thanks.]
>
> [... long post skipped ...]
>
> Back to square one, with 3 fully consistent altern
On 9/12/12 11:27 PM, Sébastien Brisard wrote:
> Dear all,
> in previous discussions, it was decided that Interfaces (and, I
> suppose abstract methods) should *not* have a throws clause.
I probably should have responded earlier that I personally disagree
with that conclusion. What is advertised i
Hi Phil,
thanks for this answer.
2012/9/13 Phil Steitz :
> On 9/12/12 11:27 PM, Sébastien Brisard wrote:
>> Dear all,
>> in previous discussions, it was decided that Interfaces (and, I
>> suppose abstract methods) should *not* have a throws clause.
>
> I probably should have responded earlier that
On Thu, Sep 13, 2012 at 07:51:29AM -0700, Phil Steitz wrote:
> On 9/12/12 11:27 PM, Sébastien Brisard wrote:
> > Dear all,
> > in previous discussions, it was decided that Interfaces (and, I
> > suppose abstract methods) should *not* have a throws clause.
>
> I probably should have responded earli
On 09/13/2012 05:13 PM, l...@apache.org wrote:
> Author: luc
> Date: Thu Sep 13 15:13:03 2012
> New Revision: 1384363
>
> URL: http://svn.apache.org/viewvc?rev=1384363&view=rev
> Log:
> Fixed an error in rectangular Cholesky decomposition.
>
> JIRA: MATH-789
Hi Luc,
thanks for looking into this
Hello -
I've been following this mailing list for a few months, and I
feel this is a good opportunity to provide a first opinion on a topic.
I find option 2, to never check for null, the best option. But, I think
it would work even better with annotations such as package level
@NonNullByD
Hi,
2012/9/13 Gilles Sadowski :
> On Thu, Sep 13, 2012 at 01:10:41AM +0200, Gilles Sadowski wrote:
>> Hello.
>>
>> [For those who don't wish to read the whole post, please at least go towards
>> the end and indicate your preferred option. Thanks.]
>>
>> [... long post skipped ...]
>>
>> Back to sq
Hi.
On Thu, Sep 13, 2012 at 01:34:38PM -0400, Kish, Robert wrote:
> Hello -
> I've been following this mailing list for a few months, and I
> feel this is a good opportunity to provide a first opinion on a topic.
>
> I find option 2, to never check for null, the best option. But, I think
>
On 9/12/12 4:10 PM, Gilles Sadowski wrote:
> Hello.
>
> [For those who don't wish to read the whole post, please at least go towards
> the end and indicate your preferred option. Thanks.]
>
>>> [...]
All are bad arguments violating API contract,
all detected at method activation time -> I
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-dbcp has an issue affecting its community integration.
This issue
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-dbcp2 has an issue affecting its community integration.
This issue
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-digester3 has an issue affecting its community integration.
This i
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-chain2 has an issue affecting its community integration.
This issu
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
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-dbutils has an issue affecting its community integration.
This iss
Hi Phil
>>
>> Back to square one, with 3 fully consistent alternatives:
>> 1. CM to always check for null? Then "NullArgumentException" inheriting from
>> "MathIllegalArgumentException" is fine because we promise to the user
>> that
>> no NPE will ever propagate through the CM layer. [Br
25 matches
Mail list logo