Hi guys, I would propose to that instead of <antlib> calling ruper, the rupper people can provide a <ruperautoload> task (or whatever other name you want) that will do all the finding and downloading and then will invoque <antlib>.
If we do this, then we can concentrate here on the local <antlib> while someone else can take care of the external work. Jose Alberto > -----Original Message----- > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED] > Sent: 22 April 2003 07:26 > To: Ant Developers List > Subject: Re: antlib > > > > Antoine Levy-Lambert wrote, On 21/04/2003 23.23: > ... > > I would like, based on this email, to read what you find OK > and what should be changed in the antlib proposal. Once I > have the comments from everybody on the list, we might put > them together in a document - including conflicting views if > any - and vote. > > Cool. > > What I would like to see in antlibs, and that can be quite > easily done > IMHO, is to make it possible to add an 'autodownload' > attribute that can > get them from a repository, using Ruper, and versioning. > > Example: > > <antlib name="ant-contrib" version="1.2+" autodownload="true"/> > > This would use the ruper task to get the antlib and load it. > > It would just need to have the Ruper task in Ant core. > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
