[
https://issues.apache.org/jira/browse/CASSANDRA-18618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738711#comment-17738711
]
Ekaterina Dimitrova edited comment on CASSANDRA-18618 at 6/29/23 5:44 PM:
--------------------------------------------------------------------------
(:sigh, I want to see the day when we would not need any add-exports, or
add-opens added AT ALL)
Let's focus this ticket on the checks and leave the JVM options to a follow-up
one?
was (Author: e.dimitrova):
(:sigh, I want to see the day when we would not need any add-exports, or
add-opens added AT ALL)
> Update tasks configuration to run checks locally when requested
> ---------------------------------------------------------------
>
> Key: CASSANDRA-18618
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18618
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Currently CheckStyle and RAT are run with almost every single Ant target,
> which is annoying as when developing locally. The targets should be clear -
> "test" - runs the tests, "jar" - builds the project and creates jars, and
> then we should have a task "check" which runs all the static analysis, that
> is CheckStyle, RAT and Eclipse-Warnings (or whatever we decide to replace
> Eclipse-Warnings with).
> Such goal should be include in "artifacts" and we should run it instead of
> "eclipse-warnings" on CircleCI. This way building, static analysis and
> testings are clearly separated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
