Project

Profile

Help

Bug #4984

closed

The SQL extension element sources don't appear to ship in the source release

Added by Norm Tovey-Walsh almost 3 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
Documentation
Sprint/Milestone:
-
Start date:
2021-05-07
Due date:
% Done:

100%

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

Description

The Saxon resources ZIP file includes JavaDoc for the net.sf.saxon.option.sql.* extension elements, and they are present in the HE mirror repository, but they don't appear in the sources zip file.

Is that intentional, or an oversight?

Actions #1

Updated by Michael Kay almost 3 years ago

I think it might have been by intent: IIRC the idea was that the issued sources.zip contains the minimum that you need to rebuild Saxon-HE as issued (source code after preprocessing, for example) and nothing else, while the repository contains everything you are entitled to under the open source license.

We issue the SQL extensions as open source code largely to acknowledge the fact that much of the code originally came from third-party contributors. On the reasonable assumption that they licensed the code to us under the Mozilla Public License, we are obliged to make available any modifications that we make to the code, even if we only use it in the commercial products. (A curiosity of the MPL is that we are actually only obliged to make the modified code available to our commercial customers, but it's fairer and easier to make it available to everyone.)

Actions #2

Updated by Norm Tovey-Walsh almost 3 years ago

Okay. The reason I discovered this was a user reported a problem reading our documentation about how to write extension elements. That documentation uses the SQL extensions as an example and implies that the source code is available. Which it is, if you know exactly where to look. They failed to find it and ended up decompiling the class files to figure out the examples.

Seems like we should try to make that easier somehow.

Actions #3

Updated by Michael Kay almost 2 years ago

  • Category set to Documentation
  • Status changed from New to Resolved
  • Assignee set to Michael Kay
  • Applies to branch 11, trunk added
  • Fix Committed on Branch 11, trunk added

I have amended the documentation for the SQL extension instructions to include a link to the repository.

Actions #4

Updated by Debbie Lockett over 1 year ago

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

Bug fix applied in the Saxon 11.4 maintenance release.

Please register to edit this issue

Also available in: Atom PDF