kezhuw commented on PR #471: URL: https://github.com/apache/curator/pull/471#issuecomment-1667757373
I verified this with two successive `mvn clean verify` on `HEAD` of this pr. The last one completes without run tests. After changes to one test file in `curator-recipes`, `mvn clean verify` runs no tests from `curator-framework`. I see the value of this pr(incremental test) and I think Gradle is building something great, but it cloud also puzzle people without any concepts of local cache (especially test cache ?). In most people's knowledge, `mvn clean verify` will run all tests from ground up. It would be really great that `mvn clean` cloud clean the corresponding test cache in this sense. I think we can go with either way: 1. Document the local cache behavior(including this pr) and way to bypass or disable them. 2. Enable this through explicit configuration. I certainly want to taste it if we finally go this way and the "explicit" could be configurable. @eolivelli @tisonkun What do you think ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
