Hi Symphoni, On Thu, Dec 17, 2020 at 12:55 AM Symphoni Bush - NOAA Affiliate < symphoni.b...@noaa.gov> wrote:
> I am trying to find out if there are any end-of-life versions for > XercesImpl, and if so, when do these versions typically become > EOL/unsupported? If this information is publicly stored anywhere please let > me know. Thanks. > Xerces-J had released a new version (2.12.1) during Jan 2020 (which I believe is fairly recent). I believe that, Xerces-J team has never officially declared any of its versions as EOL (or, that when specific version(s) would reach EOL). We definitely, do encourage Xerces-J users to use the latest released version (since, that has best possible functional implementation and quality). Interestingly, I'm keen to start a new thread of discussion, on the Java version that we should use to build any of our future releases. Currently, we're set at Java 1.3 for the release make from trunk (that also includes XSD 1.0 implementation), and Java 1.4 for the release made from our xsd 1.1 dev branch (that also includes XSD 1.0 & 1.1 implementations). I wonder, whether this is ok, keeping in view what Java version most of the Java users use these days? Java these days is at 15 version I guess. I've been thinking to propose following, to Xerces-J dev team, these days, We should make a new Xerces-J platform reorganization release. At the moment, we don't have anything major functionality to add to Xerces-J. This new platform reorganization release, should be build with say Java 1.7/1.8, and should be simultaneously support our current ANT build process & a new release also on Maven central. @ Apologies, that I'm copying this mail to Xerces-J dev list as well. -- Regards, Mukul Gandhi
