Re: IntelliJ setup for develop
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 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 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 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 >>> 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 >> >
Re: IntelliJ setup for develop
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 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 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 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 >>> 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 >> >
Re: IntelliJ setup for develop
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 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 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 >> 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 >>> >
Re: IntelliJ setup for develop
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 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: > >> 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 >>
Re: IntelliJ setup for develop
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: > 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 >
IntelliJ setup for develop
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
Re: Hostname validation
Are you using a DNS Name in the SAN section of your certificate? > On Jul 22, 2019, at 12:23 AM, Mario Kevo wrote: > > Hi, > > When SSL is enabled and ssl-endpoint-identification-enabled flag is set > to true, hostname validation is performed while establishing a > connection. This includes checking the hostname and IP address in the > certificate. In past releases, if hostname validation was disabled, a > warning log message would pop up saying hostname validation will become > mandatory in future Geode releases. This message has been removed in > recent releases, but we would still like to check whether there is a > plan to mandate hostname validation. The reasons for asking are the > implementation problems in cloud native applications with hostname and > IP validation. The IP address can change after each restart, and it > would be extremely cumbersome maintaining that in the certificates. And > in general, sticking to specific IP addresses doesn’t go in line with > cloud native principles.
