Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Turn on Config Cache File Locally for Developers #3487
http://checkstyle.sourceforge.net/config.html#Checker property cacheFile.
I want to turn that on locally, but currently the only way to do that is to modify the config for each branch I make.
I assume we can make like a maven property which we can override locally that will set it when we run the checkstyle, that way it doesn't change CI behavior and turn it on there.
When I run locally in Eclipse, I can run it either through maven:
or directly running
It appears we do set the location for the cache file in the ant-phase-verify, but we don't use it anywhere in the configuration:
Seems all we have to do is add it to the configuration file and developers can hook into it, through maven or ant or any other process.
Question: Is it safe to put the cache file into the build directory? Seems like it could accidentally get picked up in the maven
This was referenced
Oct 2, 2016
yes we should activate cache in our config -
No changes on Travis is required, as it should do all validation without any cache to avoid any leak of violations due to cache problems.
Please rename file from "cachefile" to "checkstyle.cache" to make it clear that that is not maven file.
yes, when you run "mvn clean ...." you force maven to clean all caches and .... from all plugins and phases. If smb want to reuse he need to not use "clean" phase in his commands.
@romani Because we don't support multi-file validation (
To continue with this issue we must disable the check in the default config and have a special CI only config for it. There are already a few checks that will only show up in CI (IntelliJ).
Our only other option is to abandon this issue completely until multi-file validation can be sorted out.
We should not disable this Check in our config as we have a rule to use all Checks. Yes, we have problems , fortunately it will not be a problem for users, it will not be a problem for CIs, it might be a problem for contributors (but very rare use case, unlikely to happen). Contributors will come to us and we will explain this.
@rnveach , We should enable caching by default to let you do development verification stage quicker.