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 able to successfully do XercesJ builds locally (both from trunk and branch xml-schema-1.1-dev) with command 'build clean all'. Please verify and let us know, if these XercesJ codebase changes, have resolved the issues you've been facing. On Mon, Nov 27, 2023 at 4:11 PM Michele Locati <[email protected]> wrote: > Yep, now I'm able to compile the schema-1.1 version Xerces-J by using > the xml-schema-1.1-dev branch! > > I also created a GitHub Action that does it: you can see the steps I do at > https://github.com/mlocati/compile-xercesj-schema-1.1/blob/main/.github/workflows/compile.yml > > And you can see at > https://github.com/mlocati/compile-xercesj-schema-1.1/actions > everything works, thank you! > > Just a couple of notes though. > > First of all, could you change the svn:eol-style property of the > build.sh file from "native" to "LF"? > I'm asking because I think the source distribution files available at > https://xerces.apache.org/mirrors.cgi#source have been built using > Windows, so the build.sh script included in those tarballs have > Windows line endings, and that breaks shell scripts. > Indeed, if I try to execute the build.sh script included in those > tarballs I have this error: > > : not found 20: > : not found 21: echo > Xerces-Java Build System > ------------------------ > : not found 24: > ./build.sh: 35: Syntax error: word unexpected (expecting "in") > > In order to fix it, I have to replace \r\n with \n, for example with > sed -i 's/\r$//' ./build.sh > > > Furthermore, there are two "strange" characters in > src/org/apache/xerces/impl/xs/models/XS11CMRestriction.java that break > the compilation unless you launch build.sh with the LC_ALL environment > variable set to C.UTF-8 (see for example > https://github.com/mlocati/compile-xercesj-schema-1.1/actions/runs/7003512616/job/19049394085 > ). > Since those two strange characters are in comments, I think we can > safely remove them (see attached > remove-strange-chars-from-XS11CMRestriction.java.patch). > > Thank you again! > Michele -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
