Dear Roman,
I'm sorry, I didn't realise you wanted a followup from myself for this mail.
For point (1) I would be interested in the C++ version. The other
points are related to Java only, and so I can't really address these;
while I'm also familiar with using Xalan-J, I'll likely not have much
time to work on it.
However, regarding point (4), for C++ there is also Qt XmlPatterns,
which is an XSLT2 processor. I've been doing some testing over the last
month or so, and while it's not a direct drop-in replacement for Xalan
(some of the Xalan XSLT1 quirks are not implemented, primarily related
to namespace URI/prefix transformation), it's clearly much more up to
date, albeit with a dependency upon the Qt core libraries. Probably not
too much work to convert existing transforms to work with it.
A few months back, I left the job which had a codebase heavily reliant
upon Xerces-C++ and Xalan-C++, and for which I was working on and
providing patches for both as part of that role. While I'm still doing
some contract work relating to these codebases, my current clients do
not want the Xerces or Xalan dependencies, and so I'm allowing QtXml and
QtXmlPatterns to be used as alternatives as a compile-time option. My
time for working on Xerces and Xalan from now on will be further
restricted as I start a new job working on something entirely different.
To be completely clear about the level of commitment I can provide, I'm
willing to apply the existing patchset, plus the cmake build work, and
to make a new release containing these changes, and any other
outstanding bugfixes anyone else has which need testing and reviewing.
However, for actual ongoing development, I'm afraid that my commitments
here can't be more than minimal. Xalan needs a lot of work to bring it
up to modern C++ standards, and that could be a full-time job for someone.
If you're happy with that, I'll be able to do the above. If, however,
this commitment isn't sufficient, then it might be for the best to
consider shuttering the project entirely in the absence of any other
volunteers.
Kind regards,
Roger
On 16/02/2019 22:14, Roman Shaposhnik wrote:
Ping! It has been a month and it seems that nobody has chimed in on
the questions that Gary provided below.
Does this mean that despite all efforts of late Xalan community is no more,
or does it mean that basically it is up to Gary to actually answer them?
Bill, Roger, unless you guys show some level of activity -- I don't think the
proposed resolution makes much sense.
Thanks,
Roman.
On 2019/01/16 12:49:23, Gary Gregory <garydgreg...@gmail.com> wrote:
Hi All,
Roman: Thank you for following up.
I think there a couple of worthy items to discuss:
- Which Xalan components are we still interested in? We have both a C and a
Java version.
- Does the Oracle JRE still contain a fork of Xalan-J? What are the
differences?
- When we talk about Java, should we restrict the conversation to LTE
releases like Java 8 and 11?
- Saxon-HE feels so far ahead of Xalan now. Are there other XSL processors
out there that are free and/or FOSS?
- In light of Saxon, keeping Xalan-J alive seems more of an exercise in
maintenance. Selfishly, it would help me at work, but I might be more
inclined to spend my time to port to Saxon TBH, instead of waiting for XSL
2 support in Xalan-J for example.
I'm sure there is more but that seems like a start ;-)
Gary
On Tue, Jan 15, 2019 at 7:27 PM Roman Shaposhnik <r...@apache.org> wrote:
Hi!
apologies for delaying this by a couple of weeks -- holiday break and
$DAYJOB
are to blame. Here's the resolution I'd like to consider submitting for
the next board
meeting to re-establish Xalan PMC. Not that I'm proposing this in a form
of a resolution,
but there may be other procedural ways to accomplish the same -- which I
will discuss
at the board meeting tomorrow. Still, the official part of it is going to
look something like:
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to continue maintaining a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to XSLT processors in Java and C++.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Xalan", continues
its operation pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the new members of the
Apache Xalan Project:
* Bill Blough <billblo...@apache.org>
* Roger Leigh <rle...@apache.org>
* Gary D. Gregory <ggreg...@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary D. Gregory
be appointed to the office of Vice President, Apache Xalan, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
