ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ara Abrahamian" <ara_...@yahoo.com>
Subject RE: Ant <project> extension, templatized build files
Date Thu, 02 May 2002 15:52:39 GMT
Btw, to make it clearer (I know there's <script/> in optional.jar), can
I use <script/> to add new mapper objects for examples? The other days I
needed a specialized mapper type but I had to write java code,
compile/package/... it. And it's used only in one project.

Ara.

> -----Original Message-----
> From: Ara Abrahamian [mailto:ara_e_w@yahoo.com]
> Sent: Thursday, May 02, 2002 8:11 PM
> To: 'Ant Developers List'
> Subject: RE: Ant <project> extension, templatized build files
> 
> Btw, maybe completely offtopic, but...
> 
> Do you have any plans to let us use a simple scripting language like
> rhino in Ant? You know it's hard to program sophisticated builds with
> those if/unless/condition/blabla tags. I want to be able to do
something
> like this when needed:
> 
> <target name="blabla" depends="dada">
> 	<script language="rhino">
> 		if( project.getProperty("x.y.z").startsWith("foo") )
> 			....
> 	<script/>
> </target>
> 
> Or basically a simple scriplet mechanism for using in cases where the
> built-in xml-ish tasks can't help.
> 
> Or is it already implemented somewhere?
> 
> Cheers,
> Ara.
> 
> > -----Original Message-----
> > From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com]
> > Sent: Thursday, May 02, 2002 1:35 AM
> > To: Ant Developers List
> > Cc: drew@paintyourselfsilly.com
> > Subject: Re: Ant <project> extension, templatized build files
> >
> > 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>
> 
> 
> --
> 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