[
https://issues.apache.org/jira/browse/CASSANDRA-18618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738397#comment-17738397
]
Jacek Lewandowski commented on CASSANDRA-18618:
-----------------------------------------------
More findings regarding the build - instead of repeat the command line args for
Java 11 and 17 in build.xml, we can load them directly from jvm-server.options
files, in particular this works:
{code:xml}
<loadfile srcfile="conf/jvm11-server.options" property="jvm11-server.options">
<filterchain>
<striplinecomments>
<comment value="#"/>
</striplinecomments>
<ignoreblank/>
<replaceregex pattern="\n" replace=" " byline="false" flags="gs"/>
</filterchain>
</loadfile>
{code}
> 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 10m
> 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]
