> I admit I know next to nothing about antlib, and in fact it > was nothing > until I googled it just now. If the code for such an <ftp> task were > made to reside in such a structure (rather than in > commons-net itself) > there would be no circularity. > > However, unless there is a general move to decouple ant, > which I would > support on general principles, I think these changes belong > on the main > stem of ant going forward. There has been more than one request/bug > report concerning these features, and these requests should > be granted > now that there is finally a means of doing so. For the time being, > Neeme Praks' contributions or something like them fill the > gap until the > next release. These are not "subsidiary" features of commons-net and > they should not be "subsidiary" features of the ant <ftp> task.
There is no general decouple-strategy yet, but - as sometimes said - with SVN and AntLibs we have the infrastructure for more fine grained development. E.g. we could make the <ftp> to itīs own AntLib and grant access to that AntLib to the commons-net-team ... Jan
