As the Eclipse Ant integration team lead and not trying to influence your decision but I thought I would give the Eclipse perspective.
Eclipse 3.1 is coming out in June 2005 as Jan indicated.
For me to have a chance to update and release Ant 1.7 within Eclipse it would be great to get an Ant release sometime in early May. Otherwise things start getting locked down pretty tightly in terms of major changes.
Put simply, to guarantee I could rev the Ant version in Eclipse I would need the new Ant version as of Monday May 9th, 2005 so I could get it into Eclipse M7 (set to release May 13, 2005)
For Eclipse M5 we started testing on 1.7alpha as part of the Eclipse milestone releases.
So far so good...gotta love having those Ant target locations :-)
Thanks
Darins
[EMAIL PROTECTED]
02/24/2005 04:01 AM
|
|
Eclipse should is "targeted for late June 2005" [1] and it would be good to
release Ant 1.7
before, so that (maybe) Eclipse could ship 1.7. Would be also a good
distribution :-)
Also starting with a new minor version (1.6 -> 1.7) we should introduce the
antlib subproject,
because that is a major step - 1.6 to 1.7 and starting modularization of
Ant.
Mmh <propertyset> & smartfrog: if you are the author you should be able to
change the license, IMO ;-)
I would also like the local properties in <macrodef>.
Jan
[1] http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_1.html
> you know, this summer will mark the two year point since Ant 1,6.0
> shipped. Which means time for Ant1.7 is nearing.
>
> What do people think is a good release schedule/timetable?
>
> Or to put it differently, what do people want in *and stable*
> before then?
>
> Things I must have:
>
> - <libraries> with security & docs.
>
> - WAR/EAR <lib> option to flatten libraries pulled in. Makes
> it trivial
> to embed <libraries> defined stuff.
>
> Things i'd like
>
> - a way of embedding files into <propertyset>, so you can do
> file-based
> loading from inside anything that takes a property file. Or some easy
> way of going <propertyfile file="foo" required="true" /> into Java
> tasks. I wrote my own element for this for the smartfrog
> tasks, and it
> was v. useful. But being LGPL I can't paste it back in :(
>
> - a way of embedding <libraries> inside a <classpath> declaration.
>
> <java classname="org.apache.axis.monitor.TCPMon" >
> <classpath>
> <libraries >
> <library project="ws-axis" artifact="axis" version="1.2" />
> </libraries>
> </classpath>
> </java>
>
> - <setproxy> to take a file of proxy settings; if file is absent do
> nothing, if present read in the props (merging in ant properties) and
> then set properties from there.
>
> - local properties in macros.
>
> - various contributed patches that have been on bugzilla for
> a while and
> look useful.
>
>
> -http tasks in sandbox to become an antlib.
>
> Should we be organised, build up a list of features and then either
> start doing them or scrub them from the list?
>
> -steve
