Il giorno lun 27 nov 2023 alle ore 19:05 Michael Glavassevich <mrgla...@gmail.com> ha scritto: > 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.
Thank you for the description of the current status of the project, Michael! At the moment, the xml-schema-1.1-dev branch already diverged from trunk, so having a build.xml in xml-schema-1.1-dev that supports building the trunk version would be a nightmare (and I don't think it's possible ATM). The easiest approach is: if someone wants the "1.0-only version" they can use trunk. if someone wants the "1.1 version" they can use xml-schema-1.1-dev. In any case, the current state of xml-schema-1.1-dev (with code both in directly in the .java files and in the patches of build.xml) seems really wrong to me... > 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. I don't fully understand what you mean with that... do you mean that the build.xml file as it is right now in xml-schema-1.1-dev should be kept as is because it makes maintainers' life easier? If so, the patches of my former message would make the maintaniers' life much easier IMHO... Just run "build all" in the two branches and you are done: you'll have the tarballs ready to be published for both branches... -- Ciao! Michele --------------------------------------------------------------------- To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org
