Hi,
> Right, so before we ship, should we tweak the script to pull the Maven
> saxon and use notices stored in our repo?
Already tried that but didn’t work as it looks like it was expecting more than
just the jar.
There may be a way around it.
For the build scripts - not it unpacking a bin not a jar:
<unzip src="${download.dir}/${saxon9.bin.zip}"
dest="${download.dir}/${saxon9.jar.dir}”/>
Copies notices files - presumable for legal LICENSE/NOTICE reasons?
<copy todir="${lib.ext.dir}/saxon9-NOTICES">
<fileset dir="${download.dir}/${saxon9.jar.dir}/notices"
includes="**”/>
Thanks,
Justin
