ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan.Mate...@rzf.fin-nrw.de
Subject RE: 1.6 migration guide?
Date Tue, 30 Sep 2003 15:00:24 GMT
Antlibs are interesting for people writing and publishing tasks and
for peoples who managing the ant installations.

Jan

> -----Original Message-----
> From: Steve Cohen [mailto:SCohen@sportvision.com]
> Sent: Tuesday, September 30, 2003 5:00 PM
> To: Ant Developers List
> Subject: RE: 1.6 migration guide?
> 
> 
> Thank you.  This is very helpful, a start, anyway, on what I 
> was after.
> If Peter has time, I would really like to see what he comes up with.
> 
> On antlib, I guess I don't understand yet why I would want to 
> do what it
> does.  I'm sure there must be some power in this concept but 
> I don't yet
> understand what that is.
> 
> -----Original Message-----
> From: Antoine Levy-Lambert [mailto:antoine@antbuild.com] 
> Sent: Tuesday, September 30, 2003 9:53 AM
> To: Ant Developers List
> Subject: AW: 1.6 migration guide?
> 
> 
> First of all, the change from ant1.5 to ant1.6 is not that drastic.
> 
> There are new tasks and extensions of existing tasks.
> 
> The most revolutionary feature is antlib. It should allow users to
> create jar files with a descriptor containing all the taskdefs and
> typedefs that are required.
> 
> This work done by Peter Reilly should also make it easier to deliver
> custom conditions, filters, ...
> 
> Really, Peter Reilly should be the one to write this migration guide.
> 
> Read the docs/manual/CoreTypes/antlib.html file,
> docs/manual/CoreTypes/custom-programming.html.
> 
> Apart from antlib, the <import/> task is certainly useful. I 
> am not 100%
> sure myself what you can do and not do with it, but in principle it is
> there to allow several build files to use a common part containing for
> instance property definitions, but also targets and whatever 
> is legal in
> a main build file.
> 
> Then <subant/> is a nice wrapper around <ant/> to run <ant/> against
a
> fileset of build files, or to run <ant/> n times against the 
> same build
> file, changing the base dir.
> 
> Other than that, there is the possibility to put normal tasks directly
> under the <project/> task (outside of any targets) which is 
> nice if you
> want to write a small build file.
> 
> Then the <ssh/> and <scp/> tasks will be very useful for deployment.
> 
> That's the main points which spring to my mind.
> 
> Antoine
> 
> -----Ursprungliche Nachricht-----
> Von: Steve Cohen [mailto:SCohen@sportvision.com]
> Gesendet: Dienstag, 30. September 2003 15:51
> An: Ant Developers List
> Betreff: RE: 1.6 migration guide?
> 
> 
> Jan, my comments are based on the fact that this is what I want as a
> user.  The point is that, as I said, I haven't been involved in 1.6
> development and I don't know much, if anything, about what these
> features are.  So I can't write this document.  But if one of the
> developers who is centrally involved can write this document, it would
> be very useful.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
> 

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