Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix XMLSchedulingDataProcessor to compile with Java 10 #252

Closed
wants to merge 1 commit into from

Conversation

ebourg
Copy link

@ebourg ebourg commented Jul 30, 2018

Hi,

The return type of the getPrefixes​() method of javax.xml.namespace.NamespaceContext changed in Java 10 from List to List<String>. This causes a compilation error in XMLSchedulingDataProcessor. Here is a fix addressing this issue.

@zemian
Copy link
Contributor

zemian commented Feb 11, 2019

Hi, thanks for submitting PR. Current master branch is using JDK8. We plan to support Java11 on the quartz-3.0.x in future, which already has this fixed.

Closing PR as invalid.

@zemian zemian closed this Feb 11, 2019
@dreis2211
Copy link

Hi @zemian . Any (rough) ETA on when quartz-3.0 arrives? The changes made in 647d3f2 seem to be also not too invasive. Maybe a backport to 2.x would be possible? At least it would be highly appreciated. After all JDK 12 is already released.

@zemian
Copy link
Contributor

zemian commented Apr 1, 2019

Hi @dreis2211, unfortunately no plan on any releases. But probably won't be for a while since there is not much activities going on. If you need this in 2.x branches, you can file a feature request and let it get worked on by whoever have the time.

@dreis2211
Copy link

The question remains - is there any plan on doing maintenance releases for 2.x anytime soon?

@zemian
Copy link
Contributor

zemian commented Apr 1, 2019

I thought I answered it above: no plan.

@zemian
Copy link
Contributor

zemian commented Apr 1, 2019

BTW, quartz-2.x does not use JDK 10, so there is no "backward" port of any sort. So I am not sure what's been requested also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants