Saxon

The Maven artefact http://central.maven.org/maven2/net/sf/saxon/Saxon-HE/9.9.1-1/ is requiring a none existing dependency and causes a build error.

To test it, download the latest Saxon-HE sources from Maven Central (http://central.maven.org/maven2/net/sf/saxon/Saxon-HE/9.9.1-1/) a) Save the sources http://central.maven.org/maven2/net/sf/saxon/Saxon-HE/9.9.1-1/Saxon-HE-9.9.1-1-sources.jar into a directory Saxon-HE-9.9.1-1\src\main\java b) The http://central.maven.org/maven2/net/sf/saxon/Saxon-HE/9.9.1-1/Saxon-HE-9.9.1-1.pom as into a directory Saxon-HE-9.9.1-1\ as pom.xml and execute the build via the Maven command "mvn install" There will be an dependency error: [ERROR] Failed to execute goal on project Saxon-HE: Could not resolve dependencies for project net.sf.saxon:Saxon-HE:jar:9.9.1-1: Could not find artifact xom:xom:jar:1.2.10 in central (https://repo.maven.apache.org/maven2)

The reason, there was a copy/paste mistake in the pom.xml xom xom 1.2.10 true Does not exist. It is likely mistaken, as you went to the Maven site: https://mvnrepository.com/artifact/xom/xom and read the misleading note: "Note: This artifact was moved to: com.io7m.xom » xom" and took the latest version number from: https://mvnrepository.com/artifact/com.io7m.xom/xom which is 1.2.10 BUT this would require a different group id. com.io7m.xom xom 1.2.10 true The above is the best solution atm. Please not there is a very new official (unfortunately broken) version https://mvnrepository.com/artifact/xom/xom/1.3.0 broken as the binary JAR includes the JAR of source, documentation and binaries and should BE only the latter. I am going to write Elliotte a mail, right away.

There were some other problems with the pom.xml provided by Maven:

1. Jave version not set, Lampda require 1.8 a build would fail
2. Dependency missing: com.ibm.icu icu4j 63.1
3. JavaDoc JAR and SRC JAR were not created
4. JavaDoc errors should only be warnings.. .. some minor improvements ..

I have added for suggestion a pom.xml derived from features I be using for the ODF Toolkit. At least this pom.xml can be used to build the sources :-)

Likely even your security signatures of the Java source files in the manifest.ml are able to be moved into the pom.xml and definitely the Maven artefact/SonaType uploads.

With this enabled, I would suggest to go with the sources to gitlab or github. ;-)

Thank you very much for providing such a nice XSLT engine! :-D

Cheers, Svante