Hi all, This issue has been resolved with jira issue XERCESJ-1732. On Tue, Nov 23, 2021 at 8:55 PM Mukul Gandhi <[email protected]> wrote:
On Tue, Nov 23, 2021 at 6:33 PM Gary Gregory <[email protected]> wrote: > >> I think we should bump the platform to Java 8 if that gives us the regex >> support we need. >> >> This is a new feature so it's ok to modernize. Java 8 is almost EOL as >> well anyway. Updating to only Java 7 feels like trading in one set of >> restrictions for another. >> > > I agree with you. > > But, currently I've an issue with my eclipse development environment, for > Xerces XPath 2.0 processor development, that doesn't allow me to upgrade to > Java 8, but max upto Java 7. > > I've been maintaining the Xerces XPath 2.0 processor, with Java 1.4 > support. For this, I'm currently using Eclipse IDE Indigo Service Release 2 > (dated 2012). That's a much older eclipse version that I'm using for XPath > 2.0 development. But I'm tied with it, because the XPath 2.0 eclipse > project that I've, has complex sets of dependencies to old eclipse IDE, > that Eclipse IDE Indigo satisfies for me. Eclipse IDE Indigo Service > Release 2, supports java compiler versions from 1.3 upto 1.7 (but not 1.8). > I've tried, using a latest Eclipse IDE for, XPath 2.0 processor > maintenance, but I do get IDE development issues with that. > > For now, I'd like to work with Java 1.7 support for XercesJ, due to the > constraints I've mentioned above. I'd (we :) surely, try to upgrade the > XercesJ Java level to 1.8 sometime in future (ideally, before the next > release, and if not then before a release after that), as I'm able to sort > my Eclipse IDE issues for XPath 2.0 development. > -- Regards, Mukul Gandhi
