[
https://issues.apache.org/jira/browse/TINKERPOP-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435334#comment-17435334
]
Stephen Mallette commented on TINKERPOP-2633:
---------------------------------------------
This really isn't our issue I don't think. The problem is with our inability to
upgrade to groovysh 3.x+ as described in TINKERPOP-2526. I brought up this
issue again when someone else described their performance issues on upgrade to
3.0, but it has really not garnered attention to the best of my knowledge. We
may need to either accept that performance of Groovy 3.x+ will never be as good
as 2.x and just upgrade or remove Groovy completely as a requirement and
perhaps keep it optional (or just leave it behind completely i suppose).
I will leave this issue open as a marker for the JDK17 blocker, though I'm not
sure it's the only one. Other dependencies like spark/hadoop may also be
trouble for this upgrade at this point.
> Support Gremlin Console on Java 17
> ----------------------------------
>
> Key: TINKERPOP-2633
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2633
> Project: TinkerPop
> Issue Type: Improvement
> Components: console
> Affects Versions: 3.5.1
> Environment: Java 17
> Reporter: Oleksandr Porunov
> Priority: Minor
>
> Currently Gremlin Console cannot be started on Java 17 following the next
> error:
> java.lang.IllegalArgumentException: Unsupported class file major version 61
>
> It would be great if Gremlin Console supports Java 17 as it is the newest LTS
> release after Java 11 and most likely people will start switching to Java 17
> sooner or later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
