Joerg Heinicke wrote, On 27/06/2003 18.41:
Geoff Howard wrote:
To David's question: I don't have an ant reference, but I don't think there's a way to do that and still do the entity include. That's why the resource Joerg pointed to exists I'd guess. You can't have entities point to the children of the root node by some magic I'm not aware of, can you??
AFAIK not.
At 04:18 AM 6/27/2003, Joerg wrote:
May I point to http://www.ct42.de/en/ch02.html?
Joerg
Why, yes you may!
- Just curious - why is this not in ant itself?
Because Ant is doing it's own mechanism, that started before you posted a reference to your project on the Ant list.
Is that what the "integration in ant" page is about? If that's a goal, perhaps we could help move it in that direction?
There were discussions in the ant community about an importing mechanism and there will be possibly on in Ant 1.6. AFAIK without any target name prefixing, i.e. with the disadvantage of having unique names over all imported files. It's based on or similar to the ProjectHelper http://cvs.apache.org/viewcvs.cgi/ant/src/main/org/apache/tools/ant/helper/ProjectHelper2.java.
This is a tad imprecise.
The <import> task is in Ant codebase since months now, and used by Centipede for much much more.
As for the ProjectHelper, it's a different thing, as import is a task that hooks into the Ant ProjectHelper.
What does your task bring more than Ant1.6's one, task name prefixing? That's trivial to add to Ant, but then we need to do it also with properties, references, etc etc.
...
What do you think?
I think that waiting for Ant1.6 is much better. Centipede also makes antlibs contain these plugin buildfiles, and adds other feature like automatic jar downloads, initialization of common variables, multi-project builds (that Cocoon needs because of blocks).
If you *really* want to help us (Ant and Centipede) in this import facility, get on the Ant list and send patches that enhance the current import task in what you need.
How do you reference base and plugin-relative files?
How do you, if ever, alias local plugin project properties?
And most of all: what prevents you with sending patches to Ant instead of continuing to focus on your proprietary import method?
It's a lot since Ant and your project knew of each other, what happened since then?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------