I started a new organisation on GitHub, antlibs. Currently antlibs contain 2 repos, ant-contrib and ant-http. Please let me know if you would like to join.
Currently, I would appreciate some help with IfTaskTest in ant-contrib which passes with Ant + Junit but fails with Maven + Surefire. Otherwise, things look good enough for a 1.0 :-) As for ant-http, there are currently 2 old issues left for a 1.1.4 milestone: running inside waitfor and saving headers as properties (perhaps it would make sense to use CookieStore and expose it as a resource collection even if that means Java 6 as a baseline). There is not pom.xml in ant-http either (yet :-) Gintas 2017-06-05 21:21 GMT+02:00 Dominique Devienne <ddevie...@gmail.com>: > On Mon, Jun 5, 2017 at 3:13 PM, Jan Matèrne (jhm) <apa...@materne.de> > wrote: > > > Some years ago there were a discussion about having ant-contrib a part of > > Ant. > > Result was that it wasn't possible due IP (and therefore legal) reasons. > > > > Having a look at the tasklist [1] there are some I would use: > > ... > > * outofdate: no idea > > > > <outofdate> was done by Peter Reilly, who's already an Ant commiter, > so that one should be OK (and we can always ask Peter). Same for <for> > IIRC. > > I was a heavy user of <outofdate> myself, which is much better than > <uptodate>. > I always felt it should have been in Ant proper, but I also didn't have a > problem adding > Ant-Contrib either, so no big deal. FWIW. --DD >
