ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <jakarta-...@ehatchersolutions.com>
Subject Re: Ant <project> extension, templatized build files
Date Wed, 01 May 2002 21:04:30 GMT
I've never seen anyone post any design or patches for integrating any kind
of templating into Ant's core.  So currently it would need to be built on
top of Ant.  I certainly welcome proposals and code patches that make it
more integrated - and can only comment on such after seeing it myself.

Ant 1.5 has decoupled ProjectHelper capability such that someone could
change how the project model is built - it does not have to be built from a
build.xml per se.  Thanks to Costin for that nice separation.  It will be
interesting to see what comes out of it.

For example, I believe Maven or Centipede could be modified to be a
ProjectHelperImpl and go straight from their project model to Ant's internal
project object model, and bypass build.xml altogether.

So, if there is something else about the Ant core that is prohibiting or
constraining such templating, by all means bring it up.  And if folks want
to toss out ideas about Ant core templating additions, I'm eager to hear
them.

Drew, are you listening?  Have a look at the ProjectHelper stuff in Ant 1.5
to see what kind of magic you can do there!

As for your example of a build "component" - certainly its not perfect at
the moment, but you can accomplish exactly what you describe using <ant> -
overriding properties and such.

    Erik

----- Original Message -----
From: "Chad Loder" <cloder@acm.org>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Sent: Wednesday, May 01, 2002 3:29 PM
Subject: Re: Ant <project> extension, templatized build files


> Your email seem to suggest that templating must be built on top
> of ant, rather than into ant itself.  I looked at Maven and
> Centipede, downloaded them and played around with them.  To be
> honest I think they offer (or try to offer) much more than I
> need.
>
> Having thought about this some more, all I really want is to be
> able to define a target in one XML file (say, win32exe.xml).
> Then I could refer to it from other XML files, setting or
> overriding properties as necessary. I think I can do this with
> the <ant> built-in tasks.  Semantically it would be kind of weird,
> because as I understand it, the top-level element must be a
> <project> with a project name and so on...but if I can get the
> functionality I need this way, I'm not too worried about the
> semantics.
>
> What do you think?
>
>          c
>
> At Wednesday 5/1/2002 01:53 PM -0400, you wrote:
> >I think its an unfair generalization to say that ant-dev is "unwilling"
to
> >deal with it.  Perhaps "uninterested" is more accurate.  Is there some
way
> >in which we committers have made it more difficult to build the
templating
> >pieces on top?
>
>
>
> --
> To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message