On 17-02-2021 00:23, Hugh Saalmans wrote:
Thanks Jody,
Having spent a few hours on it – the issue is caused by Spark using Ivy
for package management.
Pulling sub-dependencies (like JAI) defaults to Maven Central and Ivy
tries to pull the JAR if the .pom/.xml files are present. Hence it fails
because the binary isn’t there.
Workaround is to manually copy the jai_core-1.1.3.jar file to the
appropriate ~/.ivy2 directory. E.g.:
mkdir -p ${HOME}/.ivy2/cache/javax.media/jai_core/jars
cd ${HOME}/.ivy2/cache/javax.media/jai_core/jars
wget
https://s3-ap-southeast-2.amazonaws.com/minus34.com/opensource/jai_core-1.1.3.jar
this file is hosted by https://repo.osgeo.org/ which is listed as a
repository to use for (transitive) dependencies in the geotools pom file.
Ivy should be able to use that dependency information, but last time I
used Ivy was many years ago,
You should be able to add a resolver to the ivy settings; not sure if
you want to put any effert into that.
-M
_______________________________________________
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users