Refreshing IntelliJ from Gradle does NOT fix this for me. Question: why should a "./gradlew clean build" from command-line be required to get IntelliJ to work?
-Kirk On Tue, Dec 27, 2016 at 1:47 PM, Udo Kohlmeyer <ukohlme...@pivotal.io> wrote: > I had the same problem. gradle clean build did the trick for me > > > > On 12/27/16 13:45, Bruce Schuchardt wrote: > >> Actually neither refreshing from gradle nor creating a new Intellij >> project worked. I had to go to the "other" tasks under geode-core in the >> Gradle window and set "generateGrammarSource" to run before building. >> >> Le 12/27/2016 à 11:54 AM, Dan Smith a écrit : >> >>> Refreshing your project from gradle ought to work to. Eclipse users will >>> probably need to run ./gradlew eclipse and refresh their eclipse project. >>> There is a new generated-src directory that needs to be on the source >>> path. >>> >>> -Dan >>> >>> On Tue, Dec 27, 2016 at 11:28 AM, Bruce Schuchardt < >>> bschucha...@pivotal.io> >>> wrote: >>> >>> I did a pull today on my Windows 7 laptop and my IntelliJ build started >>>> failing with compilation errors looking for "OQLLexerTokenTypes". This >>>> comes from the fix for GEODE-165. Refreshing the IntelliJ build >>>> structure >>>> picked up the antlr tasks needed to generate this and other OQL source >>>> files but IntelliJ would not execute them. >>>> >>>> You either need to do a command-line build or close your IntelliJ >>>> project >>>> and import the gradle build into a new IntelliJ project. >>>> >>>> >> >
