Project

Profile

Help

Bug #5265

closed

Saxon-HE 11.1 depends on xmlresolver, could this be reflected in the maven pom?

Added by PJ Fanning about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Low
Category:
Build and release
Sprint/Milestone:
-
Start date:
2022-02-02
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
11
Fix Committed on Branch:
11
Fixed in Maintenance Release:
Platforms:

Description

Hi, Thanks for the Saxon 11.1 release. One item that I ran into almost immediately is that Saxon-HE 11.1 requires xmlresolver for running XPath expressions. There are no dependencies listed in https://repo1.maven.org/maven2/net/sf/saxon/Saxon-HE/11.1/Saxon-HE-11.1.pom

Would it be possible to add a runtime dependency in the saxon-he pom to xmlresolver in future releases?

Actions #1

Updated by PJ Fanning about 2 years ago

The code that I found the issue in is in Apache XMLBeans (class SaxonXPath). It uses net.sf.saxon.Configuration and runs into this issue:

java.lang.NoClassDefFoundError: org/xmlresolver/Resolver at net.sf.saxon.lib.CatalogResourceResolver.(CatalogResourceResolver.java:46) at net.sf.saxon.Configuration.init(Configuration.java:366) at net.sf.saxon.Configuration.(Configuration.java:229) at org.apache.xmlbeans.impl.xpath.saxon.SaxonXPath.selectNodes(SaxonXPath.java:91)

I can work around this by adding a dependency on xmlresolver in XMlBeans. Still, it feels more correct for Saxon-HE to declare this dependency.

Actions #2

Updated by Michael Kay about 2 years ago

  • Category set to Build and release
  • Assignee set to Norm Tovey-Walsh
Actions #3

Updated by Norm Tovey-Walsh about 2 years ago

Yes. I thought to myself "review the POM file before we ship" several times, but never when I was where I could file a bug so that I wouldn't fail to do it :-(

Sorry about that.

Actions #4

Updated by Norm Tovey-Walsh about 2 years ago

  • Status changed from New to Resolved

Saxon 11.1.1, released on Maven on Friday, 4 February, includes the required dependencies.

Actions #5

Updated by Norm Tovey-Walsh about 2 years ago

  • Status changed from Resolved to Closed
  • Fix Committed on Branch 11 added
  • Fixed in Maintenance Release 11.2 added

Please register to edit this issue

Also available in: Atom PDF