You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2021. It is now read-only.
This happens when building with JDK 1.8, while RELEASE_6 is JDK 1.6. These complaints probably would not be thrown, by already building the tools against JDK 1.7 or JDK 1.8. The mess seems to consists of 3 JDK versions, while the expected behavior would be, that it should build without complaints at least against JDK 1.7 or preferably altogether against JDK 1.8.
apply plugin: 'appengine'
// the below output is with / without these lines
sourceCompatibility = JavaVersion.VERSION_1_7
targetCompatibility = JavaVersion.VERSION_1_7
dependencies {
appengineSdk 'com.google.appengine:appengine-java-sdk:1.9.54'
}
:appengine:compileJava
warning: [options] bootstrap class path not set in conjunction with -source 1.7
warning: Supported source version 'RELEASE_6' from annotation processor
'com.google.appengine.tools.compilation.DatastoreCallbacksProcessor' less than -source '1.7'
1 warning
:appengine:compileJava
warning: Supported source version 'RELEASE_6' from annotation processor 'com.google.appengine.tools.compilation.DatastoreCallbacksProcessor' less than -source '1.8'
1 warning
Q: How to fix the bootstrap class path? are these compatibility flags even required?
Q: How to upgrade the RELEASE_6 of the DatastoreCallbacksProcessor to RELEASE_7 or RELEASE_8?
The text was updated successfully, but these errors were encountered:
syslogic
changed the title
task compileJava throws a "bootstrap class path not set" warning
task compileJava throws warnings
Jun 20, 2017
the build.gradle of the gradle-appengine-templates (added with the latest Android Studio wizard), does not configure the project module properly (both variables are grayed out):
alike this one can at least configure JavaCC per project module, instead the rootProject. despite it's another repository, the wrongful configuration in the template leads to follow-up issues, when using the plugin.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This happens when building with JDK 1.8, while
RELEASE_6
is JDK 1.6. These complaints probably would not be thrown, by already building the tools against JDK 1.7 or JDK 1.8. The mess seems to consists of 3 JDK versions, while the expected behavior would be, that it should build without complaints at least against JDK 1.7 or preferably altogether against JDK 1.8.Q: How to fix the bootstrap class path? are these compatibility flags even required?
Q: How to upgrade the
RELEASE_6
of theDatastoreCallbacksProcessor
toRELEASE_7
orRELEASE_8
?The text was updated successfully, but these errors were encountered: