[
https://issues.apache.org/jira/browse/CASSANDRA-18262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706012#comment-17706012
]
Maxim Muzafarov commented on CASSANDRA-18262:
---------------------------------------------
[~brandon.williams]
I just thought that switching for different JDKs require tiny management of the
classpath, so it might be good to consider different checkstyle versions for
each jdk to check the project.
I have prepared changes here:
https://github.com/apache/cassandra/pull/2249/files
I've tested it locally with jdk8 and jdk 11, and it seems to work, but I'm not
sure if it's still OK to do it this way. This way there is no need to block
this issue and wait for the JDK 8 removal.
Can you take I look?
> Switch checkstyle running only with JDK8 to be run with JDK11
> -------------------------------------------------------------
>
> Key: CASSANDRA-18262
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18262
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we run checkstyle, eclipse warnings (and probably anything else?)
> only with JDK8.
> In preparation to remove JDK8 we need to switch those to run with JDK11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
