I think the goal was for the xml-schema-1.1-dev branch to eventually become the trunk, but to still have the flexibility to build a jar that only has XML Schema 1.0 support, similar to the targets for DTD-only support. I’m not sure whether the build.xml reflects that well but I believe that was the intention. In reality, not much has been happening in this project for many years. Unfortunately by the time XML Schema 1.1 became a W3C Recommendation and the Xerces implementation was becoming stable, many of the developers became less active or had moved on to something else. Keeping the status quo on this branch and the trunk just became the path of least resistance for the handful of releases we’ve had in recent years.
> On Nov 27, 2023, at 9:39 AM, Michele Locati <mloc...@gmail.com> wrote: > > Hello everybody, > > If I'm not wrong, the source code of the "standard" xerces version is > in the "trunk" branch, whereas the "schema-1.1" version is in the > "xml-schema-1.1-dev". > > If so, in the xml-schema-1.1-dev branch we have some files that > diverged from trunk. > > So, why do we have the "prepare-src-schema11" ant target? > > Its role is to patch the source files to add schema 1.1 support, but > the source code is already modified to support schema 1.1 support. > So, what about simply integrating the patches defined in the > "prepare-src-schema11" target directly in the "xml-schema-1.1-dev" > branch? > > Also, the build.xml file of the "xml-schema-1.1-dev" branch is meant > to be used to build Xerces with schema 1.1 support, so I think the > current target "jar" should be replaced by "jar-schema11" (the same > for "jars" / "jars-schema11). > > Doing so, for example, the creation of distribution files would be > much easier: do you want to create the distribution files for the > "standard" version? Simply run "build pack-bin" in the trunk version. > Do you want to create the distribution files for the "schema-1.1" > version? Simply run "build pack-bin" in the xml-schema-1.1-dev version > (at the moment, this is not possible since "pack-bin" depends on > "jars" and not on "jars-schema11"). > > The attached simplify-schema11-build.patch files does all the above, that is: > > 1. update the .java files with the patches defined in the > "prepare-src-schema11" ant target > > 2. remove the "prepare-src-schema11" ant target > > 3. update the "jar-schema11" target so that it generates > "xercesImpl.jar" instead of "schema11-xercesImpl.jar" (that's the name > of the file included in the binary distribution files) > > 4. add to the "jars-schema11" target some missing dependencies > currently defined in the "jars" target (that is: icu4j.jar, > org.eclipse.wst.xml.xpath2.processor_1.2.1.jar, and > cupv10k-runtime.jar) > > 5. replace the content of the "compile" target with the content of the > "compile-schema11" target > > 6. replace the content of the "jar" target with the content of the > "jar-schema11" target > > 7. replace the content of the "jars" target with the content of the > "jars-schema11" target > > 8. remove the "jar-schema11" and "jars-schema11" targets. > > > Thoughts? > > -- > Ciao! > Michele > <simplify-schema11-build.patch> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-dev-h...@xerces.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org
