Bug #4158

Broken Maven Artefacts - net/sf/saxon/Saxon-HE/9.9.1-1

Added by Svante Schubert about 1 year ago. Updated 11 months ago.

Start date:
Due date:
% Done:


Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:


The Maven artefact is requiring a none existing dependency and causes a build error.

To test it, download the latest Saxon-HE sources from Maven Central ( a) Save the sources into a directory Saxon-HE-9.9.1-1\src\main\java b) The 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 (

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: and read the misleading note: "Note: This artifact was moved to: com.io7m.xom ยป xom" and took the latest version number from: 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 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: 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 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

pom.xml (8.37 KB) draft of working pom.xml Svante Schubert, 2019-03-06 18:12 pom.xml


#1 Updated by O'Neil Delpratt about 1 year ago

  • Category set to Maven
  • Assignee set to O'Neil Delpratt

Thank you for submitting this comprehensive bug issue and suggested POM file. We will investigate and apply the fixes necessary.

#2 Updated by O'Neil Delpratt about 1 year ago

  • Status changed from New to In Progress
  • Fix Committed on Branch 9.9 added

Applied the following fixes:

  • Fixed the xom location
  • Added Jave version to POM file
  • Added icu4j dependency which was missing

#3 Updated by O'Neil Delpratt about 1 year ago

From the post: the dependency on icu4j is not required to use the Saxon-HE jar only to build it. I will look to represent this in maven.

#4 Updated by O'Neil Delpratt about 1 year ago

Changed the icu4j dependency to optional.

#5 Updated by O'Neil Delpratt about 1 year ago

  • Status changed from In Progress to Resolved

#6 Updated by O'Neil Delpratt 11 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release added

Bug fix applied to the Saxon maintenance release

Please register to edit this issue

Also available in: Atom PDF