Erik Hatcher wrote, On 15/07/2003 18.30:
I'm finally getting around to trying the latest features of CVS Ant in a production environment. The <import> task will help tremendously, no question, but I've run into a couple of issues:
- I tried doing to <import>'s in the same build file, and the second import failed because it could not find the file, although it appears the relative base directory is being mangled after the first import. Or am I confused and missing something here?
Sorry, but I don't understand. Can you please post a buildfile with the problem? We can then fix it and add it to the testcases.
- Having the stuff imported *after* all the top-level items really is making things tough. I've had to move some top-level stuff specific to my concrete project into an init target since it relies on properties set from the imported build file. I'm guessing this is hard to fix though?
At first it worked this way, but then something was changed. It should not be hard.
...
[EMAIL PROTECTED] wrote, On 15/07/2003 19.16:
I agree. I had implemented an import task for 1.5.3 that processed a build file and ignored the project tag on the imported file. I messed with the 1.6 import and found it difficult at best to maintain supportability in the build files.
Can you please post examples?
The import I had implemented basically added the...
targets, properties and references from the import to the current
project in place. My build structure is now pretty common with a thin
layer of build files in
each project. Nested imports are supported and I have been using this
for months now without issues.
I can post the task and sample build file if you'd like...
It would be interesting to see :-)
Erik Hatcher wrote, On 16/07/2003 3.23:
I would *love* to see the code and some samples of its usage!
Well, all Centipede is based on it.
I gave up on the <import> task that is in CVS earlier today.... it just didn't scale the way I needed it to - nesting was problematic, and multiple <import>'s in one build file had issues.
Others are using it though.... so I feel maybe I'm missing something?
Maybe you are using it in a different way.
The way Centipede uses it is to add prebuilt targets to the buildfile.
Hence the imports are generally not nested, and each import does not need properties from other imports.
But we do have multiple imports.
Since my experience with <import> is very different, I'd be happy to check the buildfiles that fail for you and help you work it out :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
------------------------------------------------------------------------------------------------------------------------------------------ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
