List of fixes: All the change sets going into the main branch have the issue
number in their title. Pull a list of them to get that enumeration, factoring
out the work items for Maven cutover.
You can merge/rebase from master into your branch to pick up those changes. If
you really don't want t
Hi Gary,
Thanks for the thoughts.
On Sat, Jun 22, 2024 at 5:12 PM Gary Gregory wrote:
> I don't think we should release new features in a maintenance release like
> 2.7.x. A new feature should be in 2.x.0. Or it maybe be worth saying this is
> 3.0 which would happen to match the "3" of XSLT
[
https://issues.apache.org/jira/browse/XALANJ-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi resolved XALANJ-2754.
--
Resolution: Fixed
I'm resolving this jira issue as fixed. The fix for this issue has been
com
[
https://issues.apache.org/jira/browse/XALANJ-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi reassigned XALANJ-2754:
Assignee: Mukul Gandhi
> parse-json handles only JSON maps and objects but not the primit
Hi Joseph,
On Sat, Jun 22, 2024 at 7:15 PM Joseph Kesselman wrote:
> Have we agreed that the 3.0-features-on-a-2.0-base will have their own
> namespace, or be in the Xalan namespace, rather than in the XSLT namespace?
I still think that, we should keep same the namespace URI of, Xalan-J
XSLT 3.
Joe,
The CURRENT version is 2.7.3, so 2.3.0 is long gone.
Gary
On Sat, Jun 22, 2024, 9:45 AM Joseph Kesselman wrote:
> Normal semantic versioning is x.y.z, where changing z means only bug fixes
> or documentation changes, y is features added, and x is architectural
> changes. So I'd favor 2.3
Normal semantic versioning is x.y.z, where changing z means only bug fixes or
documentation changes, y is features added, and x is architectural changes. So
I'd favor 2.3.0.
But I'd also favor putting out one last 2.2.x with only bug fixes, and starting
2.3 with the Maven build and feature addi
Martin Honnen created XALANJ-2754:
-
Summary: parse-json handles only JSON maps and objects but not the
primitive values string, number, boolean nor the null value
Key: XALANJ-2754
URL: https://issues.apache.org/ji
I don't think we should release new features in a maintenance release like
2.7.x. A new feature should be in 2.x.0. Or it maybe be worth saying this
is 3.0 which would happen to match the "3" of XSLT 3.
I would expect (YMMV) that a new feature release would also contain all
current bug fixes from
Hi all,
Is is ok, if I could make Xalan-J 2.7.4 RC (to release, Xalan-J's
XSLT 3 subset implementation, from dev repos branch xalan-j_xslt3.0)
via Ant build process and make that available on this list for review?
The document
https://xalan.apache.org/xalan-j/xsl3/xalanj_xslt3.0_implementation
This is an automated email from the ASF dual-hosted git repository.
mukulg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/xalan-site.git
The following commit(s) were added to refs/heads/master by this push:
new dfcbc74a making few changes to document, des
ests_20240622-124238.xml} | 0
.../xsl3/xalanj_xslt3.0_implementation_status.docx | Bin 27428 -> 27453 bytes
.../xsl3/xalanj_xslt3.0_implementation_status.pdf | Bin 356240 -> 356240 bytes
3 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/xalan-j/xsl3/tests/AllXsl3Tests 20240622-12
atest information within
the document available for this, on Xalan-J's site
---
.../xsl3/tests/AllXsl3Tests 20240622-124238.xml| 886 +
xalan-j/xsl3/tests/README | 4 +-
.../xsl3/xalanj_xslt3.0_implementation_status.docx | Bin 27539 ->
13 matches
Mail list logo
