ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject AW: 1.7 release timetable & features.
Date Thu, 24 Feb 2005 12:01:27 GMT
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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message