ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <>
Subject RE: ant 1.5.4 : Import
Date Thu, 24 Jul 2003 15:50:07 GMT
I know ;-) To come back on track, I would still like to be able to set this
attribute if I chose to (getting the behavior I described), while you could
leave it off, and have your cake too.

As a build writer, I want to be able to protect myself from improper (IMO)
use of my build files, which would lead to the confusion I fear. But you're
free not to do that! Kenneth point is very valid too, and you could still
extract what would need to be shared into an import-only third file...

Getting back to your point, where does that leaves us for basedir?

I much prefer the restrictions I'm talking about, but maybe they could be ON
only if explicitly requested??? Dual behavior is not good, but neither is
tricky behavior... --DD

> -----Original Message-----
> From: Conor MacNeill []
> Sent: Thursday, July 24, 2003 10:53 AM
> To: Ant Developers List
> Subject: Re: ant 1.5.4 : Import
> On Fri, 25 Jul 2003 01:36 am, Dominique Devienne wrote:
> > Then have a look at what I did in the past two days to do something
> similar
> > ;-) I created an <antreturn> task that piggybacks on <ant>, and allows
> > returning properties and/or references from the called build file back
> into
> > the caller's context (Project).
> >
> > That would take care of that use case ;-) --DD
> >
> Not really - it doesn't allow for the overriding of a single target within
> another build file. It's useful anyway and probably should be added to
> <ant>
> but I don't see it as a reason to disallow importing of other projects.
> Conor

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message