> From: Steve Loughran [mailto:[EMAIL PROTECTED] > > Steve Cohen wrote: > > > Since there is apparently an Ant 1.6.4 version coming out > on May 19th > > and since Neeme Praks has already submitted a patch to > accomodate it, > > why not try to get this into that release? As the author of the > > commons-net code that Mr. Praks is relying on, and an Ant > committer, I > > would be happy to take a look at his code and "sponsor" it > for the 1.6.4 > > release. > > > > I realize that there may be other deadlines here. What do other Ant > > committers think? > > I worry about releasing any change to code without giving it time to > stabilise and beta test. Last minute "this won't break > anything" patches > always break something. Always. At least in my experience. > > If commons1.4.0 is incompatible with shipping <ftp> then yes, > we have no > choice but to upgrade. But if it is a feature enhancement, > then it needs to go into CVS_HEAD
I agree. We really need to come up with a decoupling strategy for ANT optional tasks or its future replacements. If the owners of the code on which those tasks depend, refuse to deliver them as part of their project because it adds a dependency to ANT for their projects, then we have a chicken and egg problem here. I do not think we can continue maintaining tasks for every project in the world just because they do not want to depend on ANT. There has to be a middle ground that everyone is happy about. I still think that common-net should be the owner of the future <ftp> replacement task and that they may release it on a separate JAR if they do not want to add dependencies to their main deliverable. Remember, they do not need to bundle ANT, just the "plugin" aka antlib for it. Maybe people would be less scare about it if we provide a task that is able to produce a ready to go plugin JAR containing all the pieces necessary for your antlib to work using an "antlib:<package>" URL. Do we have such a thing already, if nor it should be quite easy to do. Jose Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
