> -----Original Message----- > From: Matt Harp [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 29, 2004 9:19 AM > To: Ant Developers List > Subject: RE: Packaging new Ant tasks for submission? > > > > --- Matt Harp <[EMAIL PROTECTED]> wrote: > > > me, it's a matter of how our users get the Ant > > > tasks, which is much easier > > > if they ship with Ant. If they don't ship with Ant, > > > then we have to support > > > installing a seperate jar file for Ant users, and > > > then it also requires the > > > user to explicitly make taskdef defines in their > > > build files for each > > > Surround task they plan to use. If the tasks ship > > > > Regarding the taskdefs, you should consider shipping > > your jar with an antlib... see > > http://ant.apache.org/manual/CoreTypes/antlib.html#antlibnamespace > > > > -Matt > > If I can get my stuff submitted to Apache then I don't need > to worry about > the antlib stuff :) > > Never the less, I would still have the distribution issues > which I don't > want to deal with since Ant can easily include my tasks w/o > it affecting any > other Ant tasks. These tasks will (can) only ever be used by > a Surround SCM > user, in which case odds are they are gonna contact us anyway > if they don't > know how to use them, since the help file will point to us. > > So, can we all agree that I should submit my patch to the > list and then > whoever's in charge can add it to the codebase so that it's > in the next > release of Ant?
Matt, The proper channel is through bugzilla. Submit a bug report and attach the tasks. It is then up to the community and the committers to decide if it will be included. It sounds like the committers would rather not include the tasks. Also, support for tasks that are included with ant usually takes place on the users list. For example, ClearCase tasks, which were not developed by Rational (now IBM), are supported by the community, not Rational or IBM. Steve Loughran makes some good points about vendors controlling their own tasks. -Rob Anderson > > -matt > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
