intellij | IntelliJ plugin for Bazel projects

You are running the project via Java 1.8 and add the --add-opens option to the runner. However Java 1.8 does not support it.

So, the first option is to use Java 11 to run the project, as Java 11 can recognize this VM option.

Another solution is to find a place where --add-opens is added and remove it. Check Run configuration in IntelliJ IDEA (VM options field) and Maven/Gradle configuration files for argLine (Maven) and jvmArgs (Gradle)

The message typically entails that your JAVA_HOME environment variable points to a different Java version.

Here are the steps to follow:

• Close IntelliJ IDEA
• Open a terminal window and check your JAVA_HOME variable value:
  • *nix system: echo $JAVA_HOME
  • Windows system: echo %JAVA_HOME%
• The JAVA_HOME path should be pointing to a different path, then set it to the openjdk-17 path:
  • *nix system: export JAVA_HOME=/path/to/openjdk-17
  • Windows system: set JAVA_HOME=path\to\openjdk-17
• Open your project again in IntelliJ IDEA
• Make sure to set both source and target compatibility versions (not only the sourceCompatibility)

You should be able to build your project.

You may need also to instruct Gradle to use a different JVM than the one it uses itself by setting the Java plugin toolchain to your target version:

Current IntelliJ IDEA version requires Java 11 to run. Remove the overrides (idea.jdk file/environment variables) to use the default bundled JetBrains Runtime.

How to fix it:

• go to https://plugins.jetbrains.com/plugin/6317-lombok/versions
• download .zip with the latest version (0.34.1-2019.1)
• unpack it to ~/android-studio/plugins (use your path to Android Studio)
• restart IDE

After a while trying to find solutions to this problem, I saw that an emulator running outside android studio provides these options. To run a standalone Android Studio emulator see the official documentation or simply enter the command:

File->Settings->Tools->Emulator, and uncheck Launch in a tool window Then they will open in their own stand alone windows again.

Add mavenCentral() in Build Script

In my case the issue was solved by invalidating cache and restarting IDE. Simply go to Files -> Invalidate Caches -> Invalidate and Restart.

(String..String?) represents a flexible type with lower bound String and upperbound String? (nullable string). This is not valid Kotlin code (it's not denotable) but it is used in the compiler internals and thus in IntelliJ's hints sometimes.

(On the JVM we often see platform types using ! as in String!, which are a more specific case of flexible types)

It's Kotlin's way of saying it doesn't know whether the String type declared for payload.email is nullable or not (for instance if this is declared in Java, which doesn't distinguish those), and yet it doesn't want to enforce either of those, for convenience (hence "flexible").

As the name suggests, flexible types are flexible — a value of type (L..U) can be used in any context, where one of the possible types between L and U is needed

This means that even though the actual type of the value is "somewhere between String and String?", values of this type can be used even in places expecting String, even though the real type of that value may be String? and thus the value could be null.

This is useful because assuming it is String would mean that null checks would be marked as redundant, and assuming it is String? would force the developer to write null checks everywhere, even though they might know that this particular Java method cannot return null.

In general, it's a good practice to explicitly declare the type of a variable that you get from Java, to avoid the propagation of the platform type and the uncertainty (and unsafety) that comes with it: