You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/05/06 04:50:00 UTC

[jira] [Commented] (TINKERPOP-2703) Build on JDK17

    [ https://issues.apache.org/jira/browse/TINKERPOP-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720082#comment-17720082 ] 

ASF GitHub Bot commented on TINKERPOP-2703:
-------------------------------------------

kenhuuu opened a new pull request, #2056:
URL: https://github.com/apache/tinkerpop/pull/2056

   Fixes https://issues.apache.org/jira/browse/TINKERPOP-2703




> Build on JDK17
> --------------
>
>                 Key: TINKERPOP-2703
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2703
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: build-release
>    Affects Versions: 3.5.2
>            Reporter: Stephen Mallette
>            Priority: Minor
>
> Upgrade the build to work with JDK17. This actually is a bit of an umbrella issue covering lots of different things in TinkerPop. Early examination of this issue shows that like the move to JDK11, the change is not trivial. Known issues so far:
>  * Groovy 4.x upgrade brings some strange failures to the gmavenplus-plugin during GLV building
>  * Kryo 3.x is not compliant with JDK17
> In addition, Please look at the related linked issues for more information.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)