Peter,
1) In jakarta-avalon-cornerstone/ doing "ant hsql xdocs_alt" leaves
${apps-target}unset. The build.bat/sh file was setting this.
I guess this is indicating that all permutations must be expanded
into targets in the top level :-(
or don't use the top level file to build projects that are largely
independent ? I don't ;)
Rule #2 - http://www.joelonsoftware.com/articles/fog0000000043.html
I don't think you should be running the hsql build from the base directory
but from in the hsql directory.
I'd agree. If it were my own source tree I would not have it at
sub-project level. I'd have it at top level, but this is Apache, and
they can't support every diseased half finished idea I have at top-level
;-)
I was thinking about splitting the cornerstone build.xml into files. One just
built cornerstone while the other would be a controller for all the projects
build files. So if you wanted to rebuild all the projects (ftpserver, db,
hsql, cornerstone, jesktop, etc) then you would do something like
ant -f all.xml clean main
Kool...
or similar. Thoughts?
2) In jakarta-avalon-cornerstone/ doing "build hsql xdocs_alt" leaves
${tools.dir}still relative, but wrong. I've tried passing the property
up like so...
<target name="hsql" depends="compile" description="Delegates to
build.xml in apps/hsql">
<ant antfile="build.xml" dir="apps/hsql" target="${apps-target}"
inheritall="false">
<property name="tools.dir" value="../../${tools.dir}"/>
</ant>
</target>
... but it is not changing anything, the property is still relatively
wrong.
Any ideas?
Yep - don't use "value" to define the location of tools dir but instead do
something like
<property name="tools.dir" location="blah"/>
ahhhh.
This will resolve the tools directory completely. On my box the tools.dir
property would evaluate to
/opt/avalon/jakarta-avalon/tools
rather than just
../jakarta-avalon/tools
I'll have another go.
- Paul H
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
