Peter,
>>I'm trying to do some xdocs for the cornerstone apps (starting with
>>hsql). I'm having some problems with ${tools.dir} and it seemingly
>>inheriting from the master build.xml for cornerstone (despite
>>inheritall="false"). Could you take a look please :-) The target is
>>"build hsql docs" if you could not guess.
>>
>
>Okays - it is actually build.sh that sets the tools.dir directtory like
>-Dtools.dir=$AVALON_TOOLS
>
Cool, I can pass that up with <param>
>So as soon as you use build.[sh|bat] then the tools.dir is overidden. Hmmmm.
>Have you considered making it work more like the demo/build.xml
>
Demo does not have xdocs working either!
>The way I build demos is by cd'ing into apps/demo and then just "ant".
>
That's great Peter, but you are an Ant committer too. Some months ago
we were juggling versions of Ant that were not committed yet. Should we
use the Ant from ../jakarta-avalon/tools or not.
I used to have Jesktop apps working like that (30 build scripts). But
came to the conclusion that you could not get ant working from two
places in the same directory tree adequately.
My feeling is that no amopunt of effort with the current Ant will allow
Ant invocation at dirA/ and dirA/dirB where build.xml in the former
delegates to another in the latter.
>If you
>have a look at the build file you will notice it has a cleverly positioned
>antcall back to the base build.xml (ie ../../build.xml) to make sure
>cornerstone.jar is built. You could do the same the other apps and then you
>would not need to use build.[sh|bat] you could just use ant.
>
>yer/no ?
>
True..... But we've completely abandoned our Avalon (and possibly Ant)
newbies if we do that. It's already amazingly complicated with support
for Ant in a number of different installed or uninstalled places, and
Avalon get via two routes (CVS, nighlty download, release download)
If we go this route should we book in build.bat/sh files to those
locations. My reservations (dirA/dirB) still exist. I think we have to
make one choice as to where Ant is invoked.
Whilst I'm ranting (I apologise as all of this is a zillion hours of
your work). Newbies are *really* put of by the number of vars used in a
build.xml file. I've simplied to the inferior hard coded type for the
Phoenix Dev Kit script example.
Regards,
- Paul H
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
