FYI, this bug in Crawler4j was commented on by Lewis. We should update at the next Crawler4j release, after we switch to Java-7, as Crawler4j-3.5+ has switched to requiring Java-7.
Peter ---------- Forwarded message ---------- From: <[email protected]> Date: 8 April 2013 14:28 Subject: Re: Issue 145 in crawler4j: charsetName NullPointer exception To: [email protected] Updates: Status: Fixed Comment #4 on issue 145 by [email protected]: charsetName NullPointer exception http://code.google.com/p/**crawler4j/issues/detail?id=145<http://code.google.com/p/crawler4j/issues/detail?id=145> Integrated in this change: https://code.google.com/p/** crawler4j/source/detail?r=**e14a296409390eaba34108481b2ce7**79e0d99bbf<https://code.google.com/p/crawler4j/source/detail?r=e14a296409390eaba34108481b2ce779e0d99bbf> -- You received this message because you starred the issue. You may adjust your notification preferences at: https://code.google.com/**hosting/settings<https://code.google.com/hosting/settings> Reply to this email to add a comment.
