Tests are rebuilt because for some reason IntelliJ calls cleanTest before test.
If someone finds a way to tell it not to do that you would make some new
friends.
-Jake
> On Jul 24, 2019, at 3:37 PM, Murtuza Boxwala wrote:
>
> In my ideal world, I compile and run tests with IntelliJ. IntelliJ
Running a ‘devBuild’ once on the command line will fix up some modules,
sometimes. It doesn’t appear to help with running the acceptance tests in
geode-assembly, but (usually? often?) does allow running geode-core tests in
IntelliJ.
Cheers,
Dale
—
Dale Emery
dem...@pivotal.io
> On Jul 24, 2
In my ideal world, I compile and run tests with IntelliJ. IntelliJ is
constantly recompiling, so when you hit run, it’s usually just ready to run the
tests and the feedback loop feels much faster.
But, the “output path is not specified for modules” does seem to reappear
randomly, and apparentl
I had the same issue. Now I use the same configuration as Jens and that fixed
the issue. The only problem is that I feel the Gradle build takes longer than
IntelliJ’s build.
- Aaron
> On Jul 24, 2019, at 2:12 PM, Jens Deppe wrote:
>
> I'd suggest not trying to build with IntelliJ, but delegat
I'd suggest not trying to build with IntelliJ, but delegate to Gradle.
(Search for 'gradle' in Settings and then set 'Build and run using *Gradle*').
You can still run tests with IntelliJ (this is my preference as I feel it's
faster).
On Wed, Jul 24, 2019 at 2:03 PM Sai Boorlagadda
wrote:
> Buil
