Closed javabrett closed 6 years ago
JBake 2.6.0 uses orientdb 2.2.30. Which fixed a bunch of Java 9 issues.
Set -XX:MaxDirectMemorySize=512m
to org.gradle.jvmargs
in the gradle.properties file.
e.g.:
org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:MaxDirectMemorySize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
Thanks, setting org.gradle.jvmargs
avoids the JDK9-problematic detection-code and works.
Noting that in orientdb 2.2.30 the problem detection-code is still in-place: https://github.com/orientechnologies/orientdb/blob/2.2.30/core/src/main/java/com/orientechnologies/common/util/OMemory.java#L74 , but seems to be fixed on their develop branch.
I checked with 2.2.33 which is the latest release on the current stable 2.x branch which is compatible with jdk7 (which jbake upstream supports right now). And it's still there. The master branch has fixed it but reflects 3.x which will be only compatible with jdk8 as far as I know.
I think #2 fixed this issue.
JDK9 support will require at least one fix from upstream. Advise if you would like issues filed upstream with jbake-org/jbake. See also https://github.com/orientechnologies/orientdb/issues/6726 .
Current issue:
classpath 'org.jbake:jbake-gradle-plugin:1.1.1'