If we want to entice people to write antlibs, every little helps. We could have said the same thing about metainf.mf but we provided something in JAR to simplify that. Same argument here.
Jose Alberto > -----Original Message----- > From: Dominique Devienne [mailto:[EMAIL PROTECTED] > Sent: 11 May 2005 16:37 > To: 'Ant Developers List' > Subject: RE: [patch] FTP.java - adding support for new > features in commons-net 1.4.0 and performance improvement > > > I don't know if this is just me, > but I don't see the point of <antlib>. > > Writing the antlib.xml resource manually > and including it in the jar is trivial. > > We don't need special code for it. What > we may need is simply a little tutorial > about writing a basic AntLib, that's all, > and even that would mostly repeat existing > sections of the manual. --DD > > > > --- Jose Alberto Fernandez <[EMAIL PROTECTED]> > > > > <antjar jar="${jarname}" anturl="foo.bar"> > > > > <code dir="...." includes="**/*.class"/> > > > > <antlib> > > > > <task name="boo" classname="foo.bar.zzz.Boo"/> > > > > <scriptdef name="....">...</scripdef> > > > > <antlib> > > > > </antjar> > > > > What do you guys think. > > > --------------------------------------------------------------------- > 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]
