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, 2019, at 3:37 PM, Murtuza Boxwala <mboxw...@pivotal.io> wrote: > > 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 apparently it will disappear on its own after a few restarts > maybe…not sure. A re-import will fix the issue as well, but the > unreliability is definitely annoying. Switching to gradle makes things more > predictable at the cost of speed. I currently have both runners set as > "Default (IntelliJ)” and haven’t had issues for a couple weeks now. > >> On Jul 24, 2019, at 5:32 PM, Aaron Lindsey <alind...@pivotal.io> wrote: >> >> 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 <jde...@pivotal.io> wrote: >>> >>> 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 <sai.boorlaga...@gmail.com> >>> wrote: >>> >>>> Building/Rebuilding in IntelliJ fails with error "Cannot start compilation: >>>> the output path is not specified for modules". Any help would be >>>> appreciated. I have been following BUILDING.md[1] to setup intellij. >>>> >>>> [1] https://github.com/apache/geode/blob/develop/BUILDING.md >>>> >> >
