Also I am getting a build break on appveyor. It seems relate to puppycrawl check style. Any idea?
https://ci.appveyor.com/project/ApacheSoftwareFoundation/calcite/builds/28981761/job/hd165mjr65gj0xal <https://ci.appveyor.com/project/ApacheSoftwareFoundation/calcite/builds/28981761/job/hd165mjr65gj0xal> > On Nov 19, 2019, at 4:07 PM, Xiening Dai <xndai....@gmail.com> wrote: > > First want to thank you for woking on this. I try it today, and overall it > looks great. > > I also notice this output at the end, is this a known issue? > > Deprecated Gradle features were used in this build, making it incompatible > with Gradle 7.0. > Use '--warning-mode all' to show the individual deprecation warnings. > See > https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings > > Also is there an easy way to specify number of threads for build and test run? > > >> On Nov 19, 2019, at 5:43 AM, Danny Chan <yuzhao....@gmail.com> wrote: >> >> Thanks, it is because I open an existing mvn project, re-open a new one >> works for me. >> >> Thanks so much again for the great work, I’m still learning gradle, it >> broadly looks pretty good! >> >> Vladimir Sitnikov <sitnikov.vladi...@gmail.com>于2019年11月19日 周二下午9:23写道： >> >>>> I have tried the build with new gradle facilities and it is much faster ! >>> >>> Thank you. >>> I hope you would like that "wrong import order", "whitespace at the end of >>> the file", "wrong copyright", etc issues >>> are now reported in a diff-style, and they are auto-fixable. >>> >>>> Such as RelOptRulesTest, I run it in IDEA but it could not find the xml >>> resource file >>> >>> Oh, that's unfortunate. >>> Are you using your old project or have you re-created the project from >>> scratch? >>> >>> It cannot reproduce the issue though. >>> >>> Can you provide the stacktrace? >>> What's your IDEA version? >>> >>> For instance: >>> git clone --depth 100 https://github.com/apache/calcite.git calcite-t1 >>> Open calcite-t1/build.gradle.kts in IDEA. Select "open as project". >>> >>> Navigate to RelOptRulesTest, run it. It runs for me. >>> Well, by default it uses Gradle to execute the tests, so it is expected to >>> work. >>> It is the default under "Build / Build Tools / Gradle -> Run tests using" >>> option. >>> >>> If I select "Run tests using" == "choose per test", right-click the test >>> class and run it with IDEA runner, then it executes just fine (with IDEA >>> runner). >>> >>> If I select "build and run with == IDEA", re-execute the test, then IDEA >>> creates out/... folder with classes, but the test still works. >>> >>> In other words, all execution modes in IDEA work for me. I'm using IDEA >>> 2019.3 EAP by the way. >>> >>> Vladimir >>> >
