ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: import functionality in 1.6?
Date Mon, 02 Jun 2003 19:54:19 GMT
For the record, I didn't do anything with import... I did at one point allow
for multiple levels of imports, detecting circular imports, but I don't
believe it's still part of Costin's code base, and even then I only modified
code submitted by Nicola Ken Barozzi. --DD

> -----Original Message-----
> From: Antoine Levy-Lambert [mailto:levylambert@tiscali-dsl.de]
> Sent: Monday, June 02, 2003 2:42 PM
> To: Ant Users List
> Subject: Re: import functionality in 1.6?
> 
> Dear Tim,
> 
> A flavor of the import task is already available in ant 1.6alpha.
> There is no documentation available <AFAIK/>
> A brief look at the code (authors Costin Manolache and Dominique Devienne)
> shows that the task only has one attribute :
> <import file="full_path_to_your_xml_file"/>
> for some reason, the task does not support the usual relative paths
> (relative to project directory) available in ant.
> It would be good actually if you download ant 1.6alpha and try the task.
> There will be some new, not yet developed functionality in ant 1.6 final,
> but I do not expect tasks that have been added since 1.5.3 to be removed
> between the current 1.6alpha and 1.6 final. (I hope the other ant
> committers
> are not going to contradict me). There is no binding timeframe for
> 1.6final,
> and Conor McNeill mentioned August 2003 as a possibility.
> 
> Cheers
> 
> Antoine
> ----- Original Message -----
> From: "Tim Gordon" <tim.gordon@allustra.com>
> To: "Ant Users List" <user@ant.apache.org>
> Sent: Monday, June 02, 2003 6:32 PM
> Subject: import functionality in 1.6?
> 
> 
> > Hello
> >
> > I've heard that there will be some kind of import functionality
> available
> in
> > ANT 1.6. Can anyone give me some kind of indication of what will be on
> offer
> > and what kind of limitations it will have? I have to make a judgement
> call
> > concerning the impact on development time the current constraints of ANT
> > will have - it's all to do with honouring implied dependencies between
> > projects.
> >
> > The biggest problem we have with ANT is the lack of ability to express
> > 'depends'-style dependency expressed at the task level on a task that's
> > defined in another build.xml - this severely limits how far we can
> refactor
> > our build system. The only way I can see to do this sort of dependency
> > expression at the moment is with entities defined in DTDs, which while
> > workable isn't really what we're after as doesn't seem to be in the
> spirit
> > of ANT.
> >
> > Tim Gordon
> >
> > Allustra Limited
> > 1 Royal Exchange Avenue
> > London
> > EC3V 3LT
> > Tel 020 7464 4190
> > Tel 020 7464 4194
> > http://www.allustra.com/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> > For additional commands, e-mail: user-help@ant.apache.org
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org

Mime
View raw message