I'm not sure what I had this morning but I'm now using 2016.2.2
community edition with the same JDK you're using. Maybe it's a problem
unique to MS-Windows.
Le 8/16/2016 à 3:43 PM, Kirk Lund a écrit :
The project I'm using was created/imported today. My modules view for
geode-core shows the tools.jar in the list of the Project Settings
| Modules | Dependencies for geode-core:
geode-core_jca
geode-core_legacyDUnit
geode-core_main
geode-core_test
Here's my IntelliJ version and info (on Mac) according to the About:
IntelliJ IDEA 2016.1.2
Build #IC-145.971, built on April 29, 2016
JRE: 1.8.0_76-release-b162 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
My Project Settings | Modules | Dependencies also shows that I'm using
"jdk1.8.0_66" -- I'm not sure why that's different from the info in the
About window.
-Kirk
On Tue, Aug 16, 2016 at 3:28 PM, Bruce Schuchardt <bschucha...@pivotal.io>
wrote:
After pulling down the latest patches to IntelliJ this worked for me as
well, though it still doesn't configure geode-core to require tools.jar.
Thanks Kirk
Le 8/16/2016 à 12:21 PM, Kirk Lund a écrit :
All I know of is upgrading Gradle version to 2.14.1 on Aug 2.
I just built a new IntelliJ project for Geode myself without any problems.
I don't use the "gradle idea" target (is that what you're using?). That
produces a project that doesn't work for me. Instead I create a new
"Project from Existing Sources" like this:
1) File | New | "Project from Existing Sources..."
2) select your Geode checkout and hit OK
3) select "Import project from external model", select Gradle and hit Next
-Kirk
On Tue, Aug 16, 2016 at 10:37 AM, Bruce Schuchardt <
bschucha...@pivotal.io>
wrote:
Has something changed in project dependencies recently?
I rebuilt my IntelliJ project last Friday and found that there were
missing dependencies that broke my build. The modules geode-web_test,
geode-cq_test, geode-lucene_test, etc, did not have a dependency on
geode-core_test. That gave IntelliJ all sorts of grief until I manually
added them.
