Il giorno lun 27 nov 2023 alle ore 12:37 Mukul Gandhi
ha scritto:
> Please verify and let us know, if these XercesJ codebase changes, have
> resolved the issues you've been facing.
Yep: now setting LC_ALL to C.UTF-8 is no more needed: after
Hi Michele,
As requested by you, I've just committed the XercesJ codebase
changes (to the file XS11CMRestriction.java, on branch
xml-schema-1.1-dev), and to linux build scripts on trunk and to the
branch xml-schema-1.1-dev.
After these XercesJ codebase changes, as a sanity check, I've been
Il giorno lun 27 nov 2023 alle ore 08:59 Mukul Gandhi
ha scritto:
> You may please take latest XercesJ svn updates, and let us know,
> whether the XercesJ build issues that you were experiencing have been
> resolved.
Hi Mukul, thanks for the quick feedback!
Yep, now I'm able to compile the
Hi Michael,
On Sat, Nov 25, 2023 at 9:38 PM Michael Glavassevich wrote:
> I can’t actually check any of this right now as I’m travelling, but pretty
> sure the Xerces-J build is still using a custom Ant task that makes
> adjustments to the classpath. It’s entirely possible it’s doing the wrong
Hi Michele,
On Sat, Nov 25, 2023 at 9:17 PM Michele Locati wrote:
>
> > The compilation fails with errors like this:
> >
> > package org.eclipse.wst.xml.xpath2.processor does not exist
>
> Am I doing something wrong when I generate the jars as I described at
>
I can’t actually check any of this right now as I’m travelling, but pretty sure
the Xerces-J build is still using a custom Ant task that makes adjustments to
the classpath. It’s entirely possible it’s doing the wrong thing with more
modern versions of Java that have been released since it was
> The compilation fails with errors like this:
>
> package org.eclipse.wst.xml.xpath2.processor does not exist
Am I doing something wrong when I generate the jars as I described at
https://lists.apache.org/thread/o3s5bp5rj4hbwdmzf1bwklxl7mxqo1vx ?
If so, what should I do instead?
Otherwise, I'm
