October 2022 20:17
To: d...@xalan.apache.org
Cc: c-users@xalan.apache.org
Subject: Re: [VOTE] Moving Xalan-C to the Attic
I'll put it on the to do list. The PMC will NOT be dissolved because we are
still dealing with Xalan-J.
Gaty
On Mon, Oct 17, 2022, 13:43 Roger Leigh
mailto:rle...@codelibr
Hi Scott,
We can all “hope” for maintenance but ultimately someone needs to commit to
doing the work. That needs paying for, be it in time donated or money to pay
for someone else to do it. In my previous job I maintained an application
which was critically dependent upon Xerces-C/Xalan-C, a
n the Java side IIRC. So that would be (a) for me.
Gary
On Fri, Oct 7, 2022, 08:19 Roger Leigh
mailto:rle...@codelibre.net>> wrote:
Dear all,
It’s been over three months since my original email on this subject. There is
a related discussion about this on the Xerces-C++ mailing list just
Hi Scott,
This isn't ninja at fault. Ninja itself should have a complete dependency
graph, so its behaviour should not be materially different than traditional
make--but it's usually much faster due to the lack of pattern rules etc since
they have to be expanded up front at generation time (by
Hi Scott,
Hard to diagnose without more information. Can you build with verbose logging,
so we can see what ninja is waiting on? Does "ps" or "pstree" show any
children which have become stuck? Does it happen if you build with no
parallelisation?
It's possible there is a broken rule being e
come to a definitive consensus here which is realistic about the prospects for
this project, but that will require some active participation from the current
PMC and any other participants for it to be possible.
Kind regards,
Roger
From: Roger Leigh
Sent: 07 October 2022 13:19
To: d...@xalan.a
012:
$ git shortlog -s --oneline --all --since "01 OCT 2012"
1 Benjamin Beasley
1 Bill Blough
1 Biswapriyo Nath
1 Kvarec Lezki
182 Roger Leigh
29 Steven J. Hathaway
I would like for the PMC to vote on the future of the project. Do we
1. Reti
On 22 Dec 2020, at 08:27, wwp wrote:
>
> Hello,
>
>
> I'm attempting to build Xalan-C++ 1.12 following the build steps found at:
> https://apache.github.io/xalan-c/build.html
>
> Build environment:
> CentOS 7 (up-to-date), cmake3 version 3.17.3, gcc 8.2.0
> Xerces-C++ 3.2.3 build from the sou
Hi Paul,
I don't have a direct answer the the question, but I can't see why it
shouldn't work in principle. Could you build xerces, xalan and your
application with debug symbols and get a stacktrace so we can see where
it went wrong? Maybe it's something simple we can get fixed.
Thanks,
Hi Paul,
I would love to be proven wrong, but I'm fairly sure this isn't
possible, because I would have loved to have been able to do this in my
own projects where multiple transforms needed applying to a DOMDocument
in sequence and spent quite some time investigating it. I imagine that
thi
as possible. Likewise if you find
any missing or broken functionality.
Kind regards,
Roger Leigh
## Major changes
The focus of this release is stability and compatibility. The majority
of changes are bugfixes or portability improvements.
* Xerces-C++ versions 3.0 and newer are supported.
Hi,
I encountered this myself just last week. If it's the same cause as for
myself, and it's quite likely that it will be, check if you have
multiple copies of the Xerces-C++ and Xalan-C++ libraries and headers on
your search paths. The cause is that you're using the headers from one
versio
account when building a static
library as well.
Again, thanks for your work!
Rob
----
*From:* Roger Leigh
*Sent:* Sunday, May 31, 2020 6:12 AM
*To:* xalan-...@apache.org ;
c-users@xalan.apache.org
*Subject:* Xalan-C++ 1.12 release candidate 2
Dear all,
I have tagged and made a second release
Dear all,
I have tagged and made a second release candidate:
https://github.com/apache/xalan-c/releases/tag/Xalan-C_1_12_0_RC2
The above link includes the release notes, links to .tar.gz and .zip
archives, and the signed release tag. The full documentation is
at:https://apache.github.io/xa
ve a D
postfixed on windows.
Rob
--------
*From:* Roger Leigh
*Sent:* Friday, May 29, 2020 1:22 PM
*To:* c-users@xalan.apache.org ; Rob Conde
; xalan-...@apache.org
*Subject:* Re: Xalan-C++ 1.12 release candidate 1
Hi Rob,
atform - but this might be better handled in the xalan cmake itself.
I'm not entirely sure the conventions for this scenario.
Thanks,
Rob
----
*From:* Roger Leigh
*Sent:* Sunday, May 24, 2020 6:26 PM
*To:* xalan-...@apache.or
itself.
I'm not entirely sure the conventions for this scenario.
Thanks,
Rob
----
*From:* Roger Leigh
*Sent:* Sunday, May 24, 2020 6:26 PM
*To:* xalan-...@apache.org ;
c-users@xalan.apache.org
*Subject:* Xalan-C++ 1.12 release candidate 1
Dear
es or failures. If any
problems are found, we can investigate and fix them in an RC2, or defer
to 1.13 if appropriate. If we're confident that this is release-worthy,
then I'll call for a vote and we can make the first Xalan-C++ release
for nearly 8 years!
Kind regards,
Roger Leigh
Dear all,
The updated website is staged here:
https://xalan.staged.apache.org
All URLs under https://xalan.staged.apache.org/xalan-c will redirect to
https://apache.github.io/xalan-c/ using the redirects here:
https://github.com/apache/xalan-site/blob/stage/.htaccess
If this is genera
On 10/05/2020 00:21, Roger Leigh wrote:
*
https://github.com/rleigh-codelibre/xalan-c/tree/XALANC-792_replace_stylebook_documentation
(see README at bottom of page for example; links through to docs but
not API reference); docs can be generated with "doc-api" target if
d
Dear all,
I mentioned in an email a few weeks back that I was intending to make a
1.12 release in the near future. One of the tasks which required
completing in order to be able to do this was to make the documentation
usable. XALANC-792 is tracking this. The main problem is that the
docu
great.
Before making the release, there is some minor housekeeping to do in the
repository to update the release version, add some README updates etc.,
but the code itself has been in a releasable state since the changes
made last year.
Many thanks,
Roger Leigh
On 27/06/2019 11:06, FRANCOIS GODIN wrote:
Hi,
I am having issues when compiling Xalan 1.11 along with Xerces 3.2.0.
I’m using cmake on Windows 64 with Visual Studio 15 2017
Here is the entire log :
-
On 21/01/2016 16:17, rle...@codelibre.net wrote:
On 2016-01-21 15:27, rle...@codelibre.net wrote:
My unit test here fails with "invalid document structure". However,
the XML is well-formed UTF-8 with no BOM; it's been working fine for
years.
The difference between the exception being thrown o
24 matches
Mail list logo
