sparklemotion/nokogiri

Explore replacements for Xalan-J

Open

#1,829 建立於 2018年12月3日

在 GitHub 查看
 (13 留言) (0 反應) (0 負責人)Ruby (5,615 star) (806 fork)batch import
help wantedplatform/jruby

描述

See #1760 for more context.

The JRuby implementation of Nokogiri uses Xalan-J for XSLT support, but this thread reveals that development (and likely support) has stalled on that project.

A potential replacement, noted in the thread linked above, is Saxon. There may be other potential replacements as well.

The outcome intended for this issue is to do some exploration of replacing Xalan-J:

  • is there a replacement that will functionally support what Xalan-J supports today?
  • how difficult will a transition be?

Tagging @jvshahid and @kares for visibility

貢獻者指南

技術棧
java
領域
tooling
議題類型
research
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaXSLTNokogiri internals
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate the viability of replacing Xalan J with Saxon (or other alternatives) for XSLT support in Nokogiri. Review the discussion in issue #1760 and the linked Apache Xalan dev mailing list thread. Assess compatibility of Saxon with current Nokogiri XSLT functionality and estimate effort required for migration. Consider any existing PRs or forks that may have attempted this.