[
https://issues.apache.org/jira/browse/TINKERPOP-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721070#comment-17721070
]
ASF GitHub Bot commented on TINKERPOP-2703:
-------------------------------------------
spmallette commented on code in PR #2056:
URL: https://github.com/apache/tinkerpop/pull/2056#discussion_r1189065266
##########
pom.xml:
##########
@@ -198,6 +198,22 @@ limitations under the License.
<log4j-silent.properties>file:target/test-classes/log4j-silent.properties</log4j-silent.properties>
<muteTestLogs>false</muteTestLogs>
+ <jdk17JvmArgs>
Review Comment:
a comment with some details on why this is here and when/if all/any of it
can be removed in the future would be nice.
> 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)
