Open your Gradle tool window and find the generateGrammarSources task
under geode-core. Get its pop-up menu and check "Execute before
Build". Bob's your uncle.
Le 1/5/2017 à 2:13 PM, John Blum a écrit :
@Dan- right. There are only 2 options in IntelliJ. 1 way is with
Annotation Processors
@Dan- right. There are only 2 options in IntelliJ. 1 way is with
Annotation Processors; IntelliJ can search for processors on the classpath
(i.e. based on the project's dependencies). But as the name implies, it is
a pre-processor for annotations in source code. Think of something
like Project
Maybe you tell IntelliJ to use gradle rather than its internal delegates.
On 1/5/17 13:35, Dan Smith wrote:
John - yes, there's a new gradle task. The task that needs run is
geode-core:generateGrammarSource. For eclipse, we made the eclipse task
depend on that task. If we can figure out how to
John - yes, there's a new gradle task. The task that needs run is
geode-core:generateGrammarSource. For eclipse, we made the eclipse task
depend on that task. If we can figure out how to get intellij to
automatically run that task that sounds like the way to go.
-Dan
On Thu, Jan 5, 2017 at 12:47
In the newer IntelliJ you can actually have IntelliJ invoke the gradle
commands for build/run/build instead of its own internal implementation.
--Udo
On 1/5/17 12:45, John Blum wrote:
@Kirk - Is it part of a new (Gradle) build step to generate the Antlr
classes from source? In which case, yo
@Kirk - Is it part of a new (Gradle) build step to generate the Antlr
classes from source? In which case, you can configure IntelliJ to perform
this step during compiling I believe.
On Thu, Jan 5, 2017 at 12:39 PM, Kirk Lund wrote:
> Refreshing IntelliJ from Gradle does NOT fix this for me. Que
I believe that IntelliJ's gradle implementation will inspect the gradle
files but it does not execute any task if not invoked.
So, I assume I've you were to run the build task in IntelliJ it could
resolve this...
On 1/5/17 12:39, Kirk Lund wrote:
Refreshing IntelliJ from Gradle does NOT fix
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
wrote:
> I had the same problem. gradle clean build did the trick for me
>
>
>
>
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"
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
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
wrote:
> I did a
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
12 matches
Mail list logo
