Version 2.5's snapshot at
http://commons.apache.org/proper/commons-io/apidocs/index.html contains the
close portion.
-Original Message-
From: Alex P [mailto:student...@gmail.com]
Sent: Wednesday, August 06, 2014 02:11 PM
To: Commons Developers List
Subject: Re: [io] FileUtils
Could you
What I haven't seen anyone mention yet is my point of view as a user. I
don't mind getting back NPE - I just want an error message in the
exception when that happens. If I get back null as the text, then that
usually tells me the error is a JVM one or an unexpected one in the
library I'm using. Whe
mmons DBCP 2.0 released
On 26/03/2014 21:56, Kish, Robert wrote:
> Something is wrong with the link for DBCP's main page.
No, there is not.
> The link referenced in the release email (and at
> http://commons.apache.org/) refers to
> http://commons.apache.org/proper/commons-dbcp/
Something is wrong with the link for DBCP's main page.
The link referenced in the release email (and at
http://commons.apache.org/) refers to
http://commons.apache.org/proper/commons-dbcp/. But this page is for
version 1.4.
When I started clicking around the 1.4 page, I eventually figured out
the
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
