Thorsten Scherler:
> Hmm, works for me with and but normally doing:
> forrest -Dproject.home=`pwd`/exporter
> should work.
I did want to avoid using `pwd` though. :)
> > Any suggestion on how I can make the build go under the current
> > directory (apart from doing something like `pwd` in command line, since
> > it needs to be cross platform)?
>
> <antcall target="forrest.site">
> <param name="project.home" location="${exporter.home}" />
> <param name="project.start-uri"
> location="/summaries/${bulletin.year}/${bulletin.number}/index.html" />
> <param name="project.build-dir"
> location="${build.dir}/exporter/summaries"></param>
> </antcall>
>
> I have a main ant file in my customer which is the parent of
> ${exporter.home}.
>
> tree .
> `--exporter
>
> By changing the project.home I can invoke the site generation from my
> base app.
Ah I’ve realised I can do
<pathconvert property="cwd">
<path path="."/>
</pathconvert>
in my ant file to get an absolute pathname, so that solves the problem.
Thanks,
Cameron
--
Cameron McCormack, http://mcc.id.au/
xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED]
