Here is the reply of Antoine Levy-Lambert of the ant project.  To my surprise, 
he is willing to wait with 1.6.1 for our changes.  So contrary to my earlier 
message, I think we should go forward with our release as the code presently 
stands.  The refactorings that Daniel and I were discussing can wait for 
commons-net 1.3 or 1.2.1 or whatever we call it.

I haven't done a release before.  Jeffrey, is there documentation on what must 
be done?
--- Begin Message --- Steve Cohen wrote:

Another issue to consider. I don't know if it's strictly a 1.6.1 issue or further down the line but the ant developers should consider it.

I have been working with the jakarta-commons/net project to create a more capable system, able to detect what system its FTPClient class is connecting with. You may remember several complaints over the last couple of months about our <ftp> task not working on non-unix ftp servers. The improvements in commons/net will allow the correct server to be auto-detected in the most common cases, and in those odd cases where this is not possible, it will be possible to indicate explicitly which parser is to be used (i.e. in ant, a new parameter to the task).

Thus it will be possible to rewrite our <ftp> task to solve these long standing problems.

This version of commons-net (1.2.0) has not yet been released but can probably be released in less than a week.

It seems from this thread that these changes will come too late for ant 1.6.1. Please correct me if that's wrong. Can someone tell me what plans, if any, are contemplated for ant 1.6.2?

Steve Cohen



Steve, thanks for your email.

I have no problem waiting for the release of commons-net 1.2.0

Send in your patches for the ftp task through bugzilla.

Cheers,

Antoine


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to