Hi Rory, I did a quick browse through JIRA issues fixed for commons.net 2.0 but not commons.net 1.5 - and after filtering out those that appear to be related to the 2.0 branch only, or impossible to fix in 1.5 due to JDK-1.4 or later dependencies, I came up with the following list. Do you think it makes sense to backport any of these to 1.5.0? I guess I've sorted the list by order of increasing complexity, the first few looked like relatively simple low-hanging fruit, but I might be totally wrong of course... and, if uncertain about potential side effects of a fix, I believe I'd rather live with an 1.5.0 version with fewer features but without regressions... https://issues.apache.org/jira/browse/NET-184 FtpClient.listFiles truncates directory name beginning with a number https://issues.apache.org/jira/browse/NET-59 [net] NullpointerException on FTPClient.disconnect() if an Exception occured while FTPClient.connect https://issues.apache.org/jira/browse/NET-182 createFileEntryParser needs to null protect from a null 'key' parameter. https://issues.apache.org/jira/browse/NET-170 UnixFTPEntryParser does not handle file owner names with spaces https://issues.apache.org/jira/browse/NET-158 login in FTPClient does not always read the complete server response https://issues.apache.org/jira/browse/NET-148 Relaxed condition in __getReply causes other failures. https://issues.apache.org/jira/browse/NET-177 FTPClient fails to parse valid PASV responses https://issues.apache.org/jira/browse/NET-145 Deadlock in TelnetInputStream Thanks, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm
