ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conor MacNeill <>
Subject Re: ant 1.5.4 : Import
Date Tue, 29 Jul 2003 07:15:05 GMT
On Tue, 29 Jul 2003 04:56 pm, Nicola Ken Barozzi wrote:
> >
> > I think this is all getting too complex for <import>. What you are
> > describing is project composition where each project maintains its own
> > context, its own basedir, etc.
> AFAIK this is done with <ant>....

Not quite the same. <projectref> allowed the projects to be "running" in 
tandem and for dependencies to exist beteween the projects. e.g.

<projectref file="blah.xml" ref="blah"/>

<target name="test" depends="blah:init">
  <javac srcdir="${blah:src.dir}"/>

Syntax et al up for grabs but still very different from <ant>

> > In fact I would like to rename <import> as <include> to reinforce the
> > fact that this is its primary function. In fact the problems we are
> > seeing with import all come because it tries to do two things beyond a
> > simple #include operation - target renaming and allowing imports to
> > access resources according to their import file location.
> That was thought about, but then I looked in the XSLT spec, and import
> seems to look more like it. And it's similar to Java imports.

<import> is closer to C #include than java import.

> > The problem with <import> is that it flattens a hierarchy of project
> > files into a single project but tries to preserve some of the hierarchy
> > based on project names. Having multiple basedirs, ${basedir.X},
> > $@{basedir}, partially visible targets, etc is just a whole load of
> > complexity for very little benefit, IMHO.

> The current version is in fact made to minimize changes and keep it very
> simple, and it seems that you are coming too to my conclusions.
> The problem, as you correctly note, is not about import per se, but
> about false expectations that people try to realize with it.

Yes. I am arguing for the current <import> with some limited changes.

> My question is: what are users trying to do with it that is not in his
> scope and cannot be done with <ant>?


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

View raw message