ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Louis BOUDART" <>
Subject Re: EasyAnt project
Date Tue, 28 Oct 2008 15:38:51 GMT
2008/10/27 Stefan Bodewig <>

> I've given in and used my googlemail account for the easyant group,
> grmbl.

Nice :)
"Google 1 vs Stefan Bodewig 0
Round 2... Fight !"

> I'll look through the patch and will comment/start new threads for
> them later (maybe more than just a bit later).
> Since you are using Ant's trunk anyway, if we decide to add parts of
> the patch or a similar patch to achieve the same, you could modifiy
> your patch and required baseline of ant, right?

No problem.

> > - introduce "phase" concept : A kind of target that contains
> > *ONLY*dependencies,
> I'm not good at names.  I understand why this is a good name in the
> context of EasyAnt but struggle with the same name when applied to
> "pure" Ant.
> I recall being confused by the phase mapping when Xavier first
> suggested it.

We can use write java classes without using abstract classes / interface and
all that stuff? :p
Phase is like an "abstract task" it doesn't introduce order in your build
script but introduce a kind of "comportement"
<phase name="report" description="generate reports related to your
<target name="javadoc" depends="whatever" phase="report">
<target name="checstyle-report" depends="checkstyle,whatever"

By typing ant checkstyle-report you only generate checkstyle report.
By typing ant javadoc you only generate javadoc report.
By typing ant report you generate ALL targets related to the report phase.

This allow you more modularity than creating a target like :
<target name="report" depends="javadoc,checkstyle-report"/>

Is it more clear?

> > - introduce two different kind of import (what we call use /
> > extends)
> I think you will quickly find support for this separation here, in
> particular if we throw in user definded prefixes where the writer of
> the build file that uses another build file gets to define the prefix
> of targets - hi, DD ;-)

I really not understand what you mean here :'(

> > - modify project-help to display phases separated from targets
> If the concept of a phase is different from that of a "plain" target,
> then it deserve its own logging, agreed.
> Cheers
>        Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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