> -----Original Message----- > From: Matt Harp [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 29, 2004 7:48 AM > To: Ant Developers List > Subject: RE: Packaging new Ant tasks for submission? > > > >Hi, > > > >you should make a tar file with your new tasks and attach it to a bug > >report in BugZilla. > > So if I'm creating new directories I should manually add > those to the tar > file, right? > > Will making it a bug report get it submitted?
Not necissarily. First make a bug report. Then, you should initiate a discussion on the users list to see who is interested in these new tasks. Urge those who are interested to go vote for the bug in bugzilla. Bug reports with more votes get the attention of the committers. It is very democratic. -Rob Anderson > I just don't > want it to get > lost in the clutter... My process/knowledge is pretty much > dictated by what > I read here: http://ant.apache.org/ant_task_guidelines.html > is why I ask. > > > > >But maybe before you do this, can you discuss on the list what these > >tasks are about ? > > > >Antoine > > My new tasks all have to deal with integration into Surround > SCM by Seapine > Software (www.seapine.com). I work for Seapine and have > written the tasks > and we already ship them in our releases, but we would prefer > to have these > included in the Ant releases just like Perforce, ClearCase, > Sos, Cvs, Pvcs, > etc are. So I'm in the process of getting ready to submit our > Ant code and > turn it over to the Apache project so that it can be included > in the Ant > releases. I'm hoping it can be included in the next release, > but I'm not > real familiar with when that is scheduled to happen... > > > Right now my stuff is setup to use the > "org.apache.tools.ant.taskdefs.optional.surround" namespace, > which mimics > how most of the other SCM tasks currently in Ant are grouped. > > Any questions/comments/feedback welcome, > > 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]
