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 last updated. When I last did a Xerces release (years ago), I always compiled Xerces using ancient JDKs (Java 1.3 and 1.4). Hopefully Mukul chimes in on this thread as he would have the most recent knowledge of how we’ve been building releases.
> On Nov 25, 2023, at 8:47 AM, Michele Locati <[email protected]> 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 > https://lists.apache.org/thread/o3s5bp5rj4hbwdmzf1bwklxl7mxqo1vx ? > > If so, what should I do instead? > > Otherwise, I'm wondering how the binary files available at > https://xerces.apache.org/mirrors.cgi#binary have been built without > this patch... > But I managed to build the jars with "build.sh jars-schema11" after > the changes described in the attached fix-build-jars-schema11.patch > file. > Could someone with write access merge them (I think in the > xml-schema-1.1-dev branch). > > Also, could you please apply the changes in the attached > fix-build.sh-eol.patch file? > That way, the build.sh file will always have posix line endings (in > particular, think at the case when the distribution files are built on > a Windows machine). > > Thank you! > Michele > <fix-build-jars-schema11.patch> > <fix-build.sh-eol.patch> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
