No need for a separate ant branch. That's what git history is for.
I was looking at this today and moving to Maven will be a bit of slog.
A lot of this code is very strange by 2025 standards. There's a lot of
work to do first. In particular, not all the tests are based on JUnit.
They're manually e
Hi Svante,
I agree with you on following points, with few of my own suggestions as
well.
1) Including Xerces XML Schema 1.1 test suite files with XML Schema 1.1
implementation sources. This should be straight forward I think, as a
folder include.
2) Having Xerces Maven build as preferred over
Dear Elliotte, Dear Mukul,
On Sun, 12 Jan 2025 at 13:27, Elliotte Rusty Harold
wrote:
> On Sun, Jan 12, 2025 at 7:58 AM Mukul Gandhi
> wrote:
> >
> >
> > This is true, while having GitHub as repos source. But for the next
> Xerces-J release I've a feeling that we can make a release without
> im
On Sun, Jan 12, 2025 at 7:58 AM Mukul Gandhi wrote:
>
>
> This is true, while having GitHub as repos source. But for the next Xerces-J
> release I've a feeling that we can make a release without implementing this.
> A question definitely comes that, whether we should delay the next release
> fo
Hi Svante,
On Wed, 8 Jan, 2025, 15:04 Svante Schubert,
wrote:
A new Xerces-J release is indeed great news!
>
To have Xerces-J's 2.12.3 release, someone needs to prepare RC from
Xerces-J's sources from GitHub repos and have RC reviewed by subscribers of
this list. I'm curious, whether other than
Hi Mukul,
A new Xerces-J release is indeed great news!
We both desire the same for Xerces to always be high-quality, stable and
without regressions.
The common practice to achieve this is automated regression tests - like
using GitHub functionality of automated builds and tests in the GitHub
clou
Hi Svante,
I've been thinking of proposing making a new Xerces-J release.
There are various new code changes on Xerces-J's repos, that I think
are important enough for having a new Xerces-J release.
Xalan-J's XSL 3 latest code also requires the new Xerces-J release.
I'm really not sure how to
Hello Mukul,
Thanks for your contribution.
What is your plan to bring all these branches together?
In general, we should avoid duplicated data, right?
Kind regards,
Svante
PS: I asked about the Xerces tests some months ago. We should add a GitHub
regression test that always runs after every com
