After upgrading from JDK 1.8.0_152 to 1.8.0_172, I think my command-line builds are behaving better.
Next IntelliJ failure was https://intellij-support.jetbrains.com/hc/en-us/community/posts/360000162670-In-2018-1-1-version-Problem-with-Error-cannot-start-process-the-working-directory-idea-modules-does-not-exist- which didn't clear up until I upgraded from 2018.1 to 2018.1.5. IntelliJ 2018.1.5 plus JDK 1.8.0_172 seems to work together on latest develop. On Mon, Jun 25, 2018 at 2:02 PM, Kirk Lund <kl...@apache.org> wrote: > I'm also seeing two problems on the command-line. 1) occasionally a build > (without tests) will hang in one the compile targets and 2) I just started > seeing occasional out of memory errors building with gradle (see below). > > *> Task :geode-lucene:compileTestJava* > > > > The system is out of resources. > > Consult the following stack trace for details. > > java.lang.OutOfMemoryError: Java heap space > > at com.sun.tools.javac.file.ZipFileIndex.readBytes( > ZipFileIndex.java:380) > > at com.sun.tools.javac.file.ZipFileIndex.read( > ZipFileIndex.java:359) > > at com.sun.tools.javac.file.ZipFileIndexArchive$ > ZipFileIndexFileObject.openInputStream(ZipFileIndexArchive.java:151) > > at com.sun.tools.javac.jvm.ClassReader.fillIn( > ClassReader.java:2510) > > at com.sun.tools.javac.jvm.ClassReader.complete( > ClassReader.java:2442) > > at com.sun.tools.javac.jvm.ClassReader.access$000( > ClassReader.java:76) > > at com.sun.tools.javac.jvm.ClassReader$1.complete( > ClassReader.java:240) > > at com.sun.tools.javac.code.Symbol.complete(Symbol.java:574) > > at com.sun.tools.javac.code.Symbol$ClassSymbol.complete( > Symbol.java:1037) > > at com.sun.tools.javac.jvm.ClassReader.loadClass( > ClassReader.java:2623) > > at com.sun.tools.javac.comp.Resolve.loadClass(Resolve.java:1907) > > at com.sun.tools.javac.comp.Resolve.findIdentInPackage( > Resolve.java:2146) > > at com.sun.tools.javac.comp.Attr.selectSym(Attr.java:3391) > > at com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3278) > > at com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept( > JCTree.java:1897) > > at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:576) > > at com.sun.tools.javac.comp.Attr.attribType(Attr.java:638) > > at com.sun.tools.javac.comp.Attr.attribType(Attr.java:631) > > at com.sun.tools.javac.comp.MemberEnter.attribImportType( > MemberEnter.java:834) > > at com.sun.tools.javac.comp.MemberEnter.visitImport( > MemberEnter.java:558) > > at com.sun.tools.javac.tree.JCTree$JCImport.accept(JCTree. > java:571) > > at com.sun.tools.javac.comp.MemberEnter.memberEnter( > MemberEnter.java:437) > > at com.sun.tools.javac.comp.MemberEnter.memberEnter( > MemberEnter.java:449) > > at com.sun.tools.javac.comp.MemberEnter.visitTopLevel( > MemberEnter.java:528) > > at com.sun.tools.javac.tree.JCTree$JCCompilationUnit. > accept(JCTree.java:518) > > at com.sun.tools.javac.comp.MemberEnter.memberEnter( > MemberEnter.java:437) > > at com.sun.tools.javac.comp.MemberEnter.complete( > MemberEnter.java:1038) > > at com.sun.tools.javac.code.Symbol.complete(Symbol.java:574) > > at com.sun.tools.javac.code.Symbol$ClassSymbol.complete( > Symbol.java:1037) > > at com.sun.tools.javac.comp.Enter.complete(Enter.java:493) > > at com.sun.tools.javac.comp.Enter.main(Enter.java:471) > > at com.sun.tools.javac.main.JavaCompiler.enterTrees( > JavaCompiler.java:982) > > > *> Task :geode-lucene:compileTestJava* FAILED > > *<**===========**--> 84% EXECUTING [2h 23m 18s]* > > > On Mon, Jun 25, 2018 at 1:11 PM, Kirk Lund <kl...@apache.org> wrote: > >> I've pulled, done a clean build, recreated my IntelliJ project and still >> see this compilation error in buildSrc: >> >> /Users/klund/dev/gemfire_CLEAN/open/buildSrc/src/test/java/o >> rg/apache/geode/javac/TestCompiler.java >> Error:(40, 23) java: cannot find symbol >> symbol: class EnsureCorrectRunsWithProcessor >> location: class org.apache.geode.javac.TestCompiler >> >> Any idea how to resolve this? (projects with a revision prior to the >> Gradle upgrade don't hit this error) >> >> On Mon, Jun 25, 2018 at 11:55 AM, Dan Smith <dsm...@pivotal.io> wrote: >> >>> Intellij should now build geode just fine with the default gradle >>> settings >>> as of 226e406. If you followed these instructions to uncheck "Create >>> separate modules per source" to get things working last week you might >>> want >>> to reimport the gradle project with the default settings. >>> >>> -Dan >>> >>> >>> On Thu, Jun 21, 2018 at 2:40 PM, Kirk Lund <kl...@apache.org> wrote: >>> > >>> > > After the recent Gradle upgrade, you might see some compilation >>> errors in >>> > > IntelliJ involving geode-pulse such as the following: >>> > > >>> > > /Users/klund/dev/gemfire/open/geode-pulse/src/main/java/org/ >>> > > apache/geode/tools/pulse/internal/service/MemberDetailsService.java >>> > > Error:(28, 46) java: package org.springframework.context.annotation >>> does >>> > > not exist >>> > > Error:(29, 38) java: package org.springframework.stereotype does not >>> > exist >>> > > Error:(30, 38) java: package org.springframework.stereotype does not >>> > exist >>> > > Error:(42, 2) java: cannot find symbol >>> > > symbol: class Component >>> > > Error:(43, 2) java: cannot find symbol >>> > > symbol: class Service >>> > > Error:(44, 2) java: cannot find symbol >>> > > symbol: class Scope >>> > > >>> > > To resolve this, open: >>> > > >>> > > Preferences -> Build, Execution, Deployment -> BuildTools -> Gradle >>> > > >>> > > There you’ll see your Geode project under the “Linked Gradle >>> projects” — >>> > > you need to select it and then deselect “Create separate module per >>> > source >>> > > set.” >>> > > >>> > > This worked for me. >>> > > >>> > > Thanks, >>> > > Kirk >>> > > >>> > >>> >> >> >
