i can't find the random int long generator method but they exist before in the
class RandomUtils.
the Math package cut many classes away,but it provide some vapid methods just
like "createLong(String str)"
but in general i like the 3.0
Gilles Sadowski wrote:
>>> A simpler policy would be to not check for "null" and let the JVM do it. As
>>> the JVM will do it anyway, it's a redundant check when the reference is not
>>> null, i.e. most of time (in legitimate usage).
>> This simpler policy seems fine to me.
>> However, it is an imp
You're right! Sorry for the noise!
Jochen
On Wed, Aug 4, 2010 at 12:25 PM, Phil Steitz wrote:
> Jochen Wiedmann wrote:
>> Thanks, Phil!
>>
>
> We missed the fact that the files are not world-readable. Sorry, my
> bad. They need to be readable by apbackup. You (jochen) need to
> either u+r or
> >>> A simpler policy would be to not check for "null" and let the JVM do it.
> >>> As
> >>> the JVM will do it anyway, it's a redundant check when the reference is
> >>> not
> >>> null, i.e. most of time (in legitimate usage).
> >> This simpler policy seems fine to me.
> >> However, it is an im
Hi,
I'd like to announce the availability of Commons FileUpload 1.2.2.
This is a binary compatible bug fix release, intended to replace all
previous versions. Binary and source distributions are available from
http://www.apache.org/dyn/closer.cgi/commons/fileupload
The list of changes, compa
Gilles Sadowski wrote:
> A simpler policy would be to not check for "null" and let the JVM do it.
> As
> the JVM will do it anyway, it's a redundant check when the reference is
> not
> null, i.e. most of time (in legitimate usage).
This simpler policy seems fine to me.
>>
> [...]
>
> > I think that using IAE instead of NPE does not bring any added value. It
> > justs goes against standard usage: throw NPE when a reference is "null"
> > and is not allowed to be so.
> > As proposed in
> > https://issues.apache.org/jira/browse/MATH-401
> > we could still do explicit
Gilles Sadowski wrote:
>> [...]
>>
>>> I think that using IAE instead of NPE does not bring any added value. It
>>> justs goes against standard usage: throw NPE when a reference is "null"
>>> and is not allowed to be so.
>>> As proposed in
>>> https://issues.apache.org/jira/browse/MATH-401
>>> we
> > As proposed in
> > https://issues.apache.org/jira/browse/MATH-401
> > we could still do explicit checks for "null" but nevertheless throw the
> > standard (non-specific and non localized) NPE.
> >
> The added value that I see is that an IAE designating which argument
> that cannot be null is
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-xml-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-jelly-tags-jaxme has an issue affecting its community
integration
Gilles Sadowski wrote:
>>> As proposed in
>>> https://issues.apache.org/jira/browse/MATH-401
>>> we could still do explicit checks for "null" but nevertheless throw the
>>> standard (non-specific and non localized) NPE.
>>>
>> The added value that I see is that an IAE designating which argument
>
Will IO 2.0 be targeting Java 1.5+ (with generics, varargs, other 1.5+
goodness) like Lang 3.0 or will it be retaining backwards
compatibility?
On Wed, Aug 4, 2010 at 1:43 AM, Henri Yandell wrote:
> Great to have you involved Lorenzo.
>
> I'm happy to help out - both with a release and if you hav
On Aug 5, 2010, at 1:29 PM, Michael Wooten wrote:
> Will IO 2.0 be targeting Java 1.5+ (with generics, varargs, other 1.5+
> goodness) like Lang 3.0 or will it be retaining backwards
> compatibility?
>
The first option. :)
-Matt
> On Wed, Aug 4, 2010 at 1:43 AM, Henri Yandell wrote:
>> Grea
Le 05/08/2010 16:26, Phil Steitz a écrit :
> Gilles Sadowski wrote:
As proposed in
https://issues.apache.org/jira/browse/MATH-401
we could still do explicit checks for "null" but nevertheless throw the
standard (non-specific and non localized) NPE.
>>> The added value tha
> >> The added value that I see is that an IAE designating which argument
> >> that cannot be null is in fact null gives more specific information
> >> to the caller (or production support person examining logs) than
> >> just a propagated NPE.
> >
> > Well, my initial post reported the inconsiste
Hello,
I just configured everything for Nexus and successfully created a snapshot:
https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-compress/1.1-SNAPSHOT/
The how to i followed:
http://wiki.apache.org/commons/UsingNexus
is very good, no objections.
I did it
Though I thought I'd read that it is currently both 1.5+ and has been
able to maintain backwards compatibility (i.e. no need to change the
package name). Something for clirr to determine once the release is
ready.
On Thu, Aug 5, 2010 at 11:39 AM, Matt Benson wrote:
>
> On Aug 5, 2010, at 1:29 PM,
18 matches
Mail list logo
