I just switch to try develop on Linux for a while.
But one thing I couldn't understand how to solve it, as I mentioned in topic.
I'm going to develop a project that need Java SDK, then I installed the SDK with command:
#bash
sudo apt install openjdk-17-jdk-headless
After installation finished, I could run command java -version and javac -version to see the result of installation and it looks OK.
openjdk version "17.0.3" 2022-04-19
OpenJDK Runtime Environment (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1)
OpenJDK 64-Bit Server VM (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1, mixed mode, sharing)
And then when I open IDE (Intellij IDEA) and it has feature of integrated terminal. (see picture)
But when I try to test java -version it was shown the error:
bash: java: command not found
As you can see from picture, I run java -version on terminal it return output properly, but when I run the same command java -version, it output with error message, like it couldn't find the java SDK that I installed.
Could anyone help me to describe the reason and solutions to solve the issue?
P.S. This is same on VS Codium.
I found the answer.
Solution:
Install the IDE app with the file from official website instead of using package manager of OS.
Description:
The cause is I installed the IDE via Package Manager of OS (here I'm using Pop_OS, install via Pop!_Shop)
And its package manager has some strict rules for security purpose.
I'm not sure, Pop_OS using which package manager, but I'll raise Flatpak as reference: https://docs.flatpak.org/en/latest/sandbox-permissions.html
And on blacklisted directories, my installed java command is under /usr/bin/ which is in blacklist.
I am using AsciidocFX version 1.7.4 to edit Asciidoc documents. When working on PlantUML diagrams and creating a syntax error, which is caused by using syntax that is not supported in older versions, I see the following message
PlantUML 1.2021.2
This version of PlantUML is 398 days old, so you should consider upgrading...
I have the following version installed on my system:
PlantUML version 1.2022.3 (Tue Mar 29 09:10:57 PDT 2022)
(GPL source distribution)
Java Runtime: OpenJDK Runtime Environment
JVM: OpenJDK 64-Bit Server VM
Obviously, AsciidocFX finds a different version. How can I configure AsciidocFX to use my latest locally install version? I went through the Settings dialogs as well as looked in the ~/.AsciidocFX-1.7.4 folder but could not find any clue.
planumtl consist of a single plantuml.jar file. You should find a plantuml-1.2021.2.jar file in your installation folder, under lib, delete it and replace it with your own version.
I have installed Android Studio Canary 2020.3.1.22 and trying to run Flutter project on Apple Silicon(ARM) Mac. Unfortunately, it is giving me this error when I try to run default flutter counter app.
Here is the error I am getting:
Could not open settings generic class cache for settings file '/Users/khamidjonkhamidov/StudioProjects/dummy/android/settings.gradle' (/Users/khamidjonkhamidov/.gradle/caches/6.7/scripts/f0emg6u6oecmxqzgk5g9nn4ui).
> BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 61
Gradle version: 6.7 but I tried 7+
JDK version 17
I would really appreciate your help)
According to the official grade docs: Java 17 and later versions are not yet supported.
You can check compatibility here.
So I have installed Java11 from Azul.
p.s. don't forget to change jdk version in Android studio
Preferences -> Build -> Build Tools -> Gradle -> Gradle JDK
Got the same error while I upgraded my build.gradle to Java 17. And the fix is as simple as we think:
Gradle starts supporting Java17 only from 7.3 release
Here's the complete reference for Java vs Gradle compatibility:
https://docs.gradle.org/current/userguide/compatibility.html
Upgraded my gradle to 7.3 in gradle-wrapper.properties.
https\://services.gradle.org/distributions/gradle-7.3.3-bin.zip
Some of you may experience now the Gradle dependency cache corrupt error after this like me. So better delete the gradle-wrapper.jar and reinstall it using the command:
./gradlew wrapper
Everything will work perfectly fine from here.
In case if you still face Gradle corrupt issue, please check whether you are using latest version of IDE especially Intellij.
First, you can execute this command: /usr/libexec/java_home -V, to retrieve all installed jdsk:
[~]$ /usr/libexec/java_home -V
Matching Java Virtual Machines (4):
17.0 (x86_64) "Oracle Corporation" - "OpenJDK 17.0" /Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-17.0/Contents/Home
14.0.1 (x86_64) "Oracle Corporation" - "OpenJDK 14.0.1" /Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-14.0.1/Contents/Home
11.0.12.1 (x86_64) "Amazon.com Inc." - "Amazon Corretto 11" /Users/ciccio/Library/Java/JavaVirtualMachines/corretto-11.0.12/Contents/Home
10.0.2 (x86_64) "Oracle Corporation" - "Java SE 10.0.2" /Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
1.8.0_302 (x86_64) "Amazon" - "Amazon Corretto 8" /Users/ciccio/Library/Java/JavaVirtualMachines/corretto-1.8.0_302/Contents/Home
Now, imagine you want to remove the version 17:
[~]$ java -version
openjdk version "17" 2021-09-14
OpenJDK Runtime Environment Homebrew (build 17+0)
OpenJDK 64-Bit Server VM Homebrew (build 17+0, mixed mode, sharing)
Go into the path of the version you want to remove (in this case "/Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-17.0/Contents/Home"), and delete entire folder: "/Users/ciccio/Library/Java/JavaVirtualMachines/openjdk-17.0".
Once removed, go back on terminal and use:
[~]$ /usr/libexec/java_home -v 14.0.1 --exec javac -version
javac 14.0.1
to force the new version to use (14.0.1).
Next check if is correct:
[~]$ java -version
openjdk version "14.0.1" 2020-04-14
OpenJDK Runtime Environment (build 14.0.1+7)
OpenJDK 64-Bit Server VM (build 14.0.1+7, mixed mode, sharing)
[~]$
Your Gradle now is back to work.
Basically, I installed jdk using brew install java which was not compatible with my current gradle I guess. So
I uninstalled java first using: brew uninstall java
installed JDK 8 or JDK 11 from azul.
Installed gradle: gradle-6.9-all.zip
When done, everything worked smoothly.
I found a way to fix this error without messing with the locally installed Java version or Gradle. Here is what I did:
If you are developing a Flutter project and got this error, go to File -> Close Project.
Then re-open from the android folder (omit this if you received from a pure Android project).
Now, Gradle may detect the issue on its own, and it will take a while to check. After it is done, it may provide upgrade steps in an upgrade assistant window at the bottom of the window along with logcat, build, terminal etc… which you need to accept and tell it to execute. Once it finishes, the error is resolved, and you are good to go.
If it does not seem to do anything on its own, then please open the Project Structure tab. Now select the latest Gradle version available that does not contain -rc (you don't want these, most of the time they are not stable releases).
Now select the JDK version that Gradle uses by going to Gradle (sidebar on the right of the window) -> Wrench Icon -> Gradle Settings. Select a compatible JDK version according to the Gradle project's documentation, as found HERE. Current latest stable version of Gradle is 7.4 with maximum supported JDK version 17 (also latest I believe if you use something like openJDK which I use), but Android Studio version at 7.1 so be careful.
Tested on MacBook Air M1 running macOS Monterey 12.2.1.
I faced this error when I updated my android studio
Solution:
you need to upgrade your distributionUrl According to the java version
Below is the Java version and Supported Gradle version
Check currently active java version:-
javac -version
If it is greater than 11 downgrade it to 11 or 8. Check your available java jdk version installed:-
/usr/libexec/java_home -V
If java 11 or 8 is not installed first install one of them using this link:- Download jdk 8
then change the default java version in .bash_profile
Edit .bash_profile
sudo nano ~/.bash_profile
Add 1.8 or 11 as default. (Add below line to bash_profile file)
export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
OR
export JAVA_HOME=$(/usr/libexec/java_home -v 11)
Now Press CTRL+X to exit the bash. Press 'Y' to save changes. And reload bash_profile
source ~/.bash_profile
Happened with newly created Flutter app in 2023 January with Mac Mini M1. If you have another working Flutter apps do not downgrade or update Java version as it will cause problem with all other working ones. Find gradle-wrapper.properities file inside gradle/wrapper folder (directly inside Android folder) and check gradle version. You just need to use newer version of gradle. I replaced this one and used flutter run command from terminal and it worked:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.5-all.zip
With this one:
distributionUrl=https\://services.gradle.org/distributions/gradle-7.6-all.zip
No need to do anything else. Version number may be different for you depending on when you are trying this and what Java version you have.
Finally I Got the Solution
It is very easy to solve
step 1 : select the gradle version which support your java version link
step 2 : open your project navigate to your_project_name/android/gradle/wrapper/gradle-wrapper.properties
step 3 : in distributionUrl change the gradle version according to your java version
That's it No need to install older java versions
Happy coding
System: Mac M1, Android Studio Electric Eel (2022.1.1 Patch 1), JDK 19.02
I encountered this error when created a fresh project using flutter create and tried to run it in Android Studio.
Now I've got an interesting solution that worked for me:
Open the flutter project in Android Studio
Open build.gradle, the one under android folder
On the top right it shows "Open for Editing in Android Studio" (although it's already in Android Studio!). Click on that to open it for editing. I opened it in another window, but doesn't matter.
It starts to automatically download and update gradle to sync the build file. At one point, tt might also prompt you to upgrade gradle, which is good to do.
Done! Close the build.gradle and re-run the project. It should build and run fine.
I had this issue when I set the target for a new IntelliJ Kotlin project to be Java 17. My fix was to:
set the target to 9 in build.gradle.kt
close the project
delete the .gradle and .idea directories from the project folder
remove the project from the recent projects list
open the gradle file from IntelliJ and get it to rebuild everything
Open the Gradle settings and change the Gradle JVM to the same JDK version you are using.
(I am using 14.0.2)
This worked for me.
I had that Issue creating Projects from IntelliJ.
It seems the issue was the Gradle JVM Version.
Here is a configuration that works:
System:
Mac with ARM, Mac OS 12.1, M1 Max
java version 18.0.1-zulu
kotlin version 1.7.0
gradle version 7.5
I installed those version with sdkman https://sdkman.io/
and set the config manually on intellij (See attached Screenshot for Details)
IntelliJ Gradle JVM config
My solution was to open the android project in Android Studio. It detected the needed Gradle update and performed the update upon command.
I can't speak for everyone, but for me, I went into Flutter project's file android/gradle/gradle.properties, and changed the org.gradle.java.home value so that it pointed to a folder containing JDK 11 instead of JDK 18. That way, it used a JDK version that was actually supported.
On my side I fixed this issue by setting the default Java Version to 8 (download it if needed)
Mac:
Open Terminal.
open ~/.bash_profile
Add
# SWITCH TO JAVA VERSION 8
export JAVA_HOME=`/usr/libexec/java_home -v 1.8`
Save and restart Android Studio.
Giving my two seconds here...
In my case, I could fix it by finding my gradle version in the file gradle.wrapper.properties and checking the compatibility with the JDK, so I needed to install the JDK 16, so in my build.gradle(:app) I put this line of code inside the android {} :
compileOptions {
sourceCompatibility JavaVersion.VERSION_16
targetCompatibility JavaVersion.VERSION_16
}
After this I build my android version again, and it worked.
I ran into this issue on VSCode+Mac using the Gradle for Java extension.
My project uses Java 17 but Gradle was using JDK19, which I also had installed.
I removed the jdk-19.jdk folder from /Library/Java/JavaVirtualMachines and then ran the "Clean Java Language Server Workspace" task in VSCode.
After that, Gradle successfully built and I was even able to put the jdk-19 folder back and things continued to work.
Changing the Java Version in the Intellij resolved the issue.
Easy fix in 2023:
Command in the terminal:
export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
Check classpath, current working one:
classpath 'com.android.tools.build:gradle:7.1.2'
Check gradle-wrapper.properities file:
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-7.4-all.zip
If still not solved you need to change Gradle JDK from inside Android Studio like below.
After that you can run fluter app directly from terminal without any issue. Note: Android Studio default JDK (11.0.15) does not work and causes this issue. Azul Zulu 16.0.2 works and solves the issue.
In my case, I use the react native cli and my android gradle is 7.3.1. I open the android folder in the android folder in the android studio and it suggests my gradle once after degradation it works fine
Windows Users
Open Android Studio and Click on Setting ICON far right. And Go to Project Structure Option and select the SDK's Version 11.0.15 and click apply than on the left side click on Module Option and select Module SDK's options and select Project SDK 11. and at the bottom at Project Settings CLICK on SDK and select on 11 SDK versions. It will give you the JDK path
C:\Program Files\Android\Android Studio\jbr
Copy this path and Open the System Environment Variable Create a New JAVA_HOME path with the location
and click OK and save everything Now run your app in ANDROID STUDIO and ENJOY!
Context: Flutter, Mac M1, Java 19.0.2
Problem occured on following command:
flutter build apk
I just installed (reintalled) gradle via homebrew like this:
brew install gradle
I suppose it was related to my recent upgrade (Java was upgraded to OpenJDK Temurin 19.0.2).
I also noticed that flutter command was trying to use gradle 7.4 (the only one gradle version installed before). As previously mentioned by others, there has to be consistency between your Java version and gradle version according to Gradle Official Compatibility Matrix.
Please, verify it with following commands:
java -version
gradle -version
I think this process / solution can be applicable in general. Hope it helps!
I have a problem with latest version of Cytoscape 3.8.0 It doesnt start. I can see only logo and than nothing. Computer is running OSX 10.13.6. I am using successfully version Cytoscape 3.7.2 but I want to upgrade. When I run script mac.sh I got following:
Target Cytoscape version: 3.8.0
Your shell is bash
Compatible OS version found: 10.13
Pass: OS Version = 10.13.6
Pass: Following Oracle JDK found:
/Library/Java/JavaVirtualMachines/jdk-11.0.7.jdk
Fail: Java is not reachable.
Try re-installing Java 11.
I can confirm that java is in place /Library/Java/JavaVirtualMachines and versions jdk-11.0.7.jdk jdk-12.0.2.jdk jdk-14.0.1.jdk
I guess that version 37 and 38 work with java 11? I have reinstalled java 11 with same results as before. Version 38 doesnt start. When I try to start version 38 from terminal with cytoscape.sh I got long error message which starts with:
Unable to find any JVMs matching version "1.8".
karaf.base: /Applications/Cytoscape_v3.8.0/framework
JAVA_HOME: null
ERROR: Error parsing system bundle export statement: org.osgi.dto;version="1.0",org.osgi.resource;version="1.0",org.osgi.resource.dto;version="1.0...
I can paste whole error message if needed.
Any idea what should i do? Thanx.
Cytoscape 3.7.x requires Java 8. Cytoscape 3.8.0 requires Java 11. It looks like your java home is incorrect. If you do:
/usr/libexec/java_home
it should point to your java 11 installation. On my mac it says:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Note that the "/Contents/Home" is important. To set your actual JAVA_HOME, do
export JAVA_HOME=`/usr/libexec/java_home -v 11`
I had this same problem. What Scooter Morris mentioned is correct, but I had to follow an additional link on stack overflow to get it fixed.
This is exactly what I did:
In my case I had to run:/usr/libexec/java_home -V to see the Java Virtual Machines I have installed and specify the V 11 using:
export JAVA_HOME=`/usr/libexec/java_home -v 11.0.7`
Then running the ./mac.sh command tells me everything checks out and Cytoscape can finnaly run :)
Edit: I should add that I can only run cytoscape by launching it from the terminal via:
cd /Applications/Cytoscape_v3.8.0
./cytoscape.sh
Clicking the app icon only results in the app crashing on load but it appears to work fine by launching it from the script. I don't have this issue on Mac OS 10.14 so maybe its a software version issue or some background app in my computer is getting in the way of launching the app normally.
I am trying to run my go script called release.go in the Goglang built in terminal and it gives me the following output
$ go run release.go
# command-line-arguments
flag provided but not defined: -goversion
usage: compile [options] file.go...
-% debug non-static initializers
...
If I run this in my terminal outside of Gogland the release.go file runs without issue.
This problem started occurring after upgrading from version 1.8.3 to 1.9 and I have never used the -goversion flag before.
Current Gogland version:
Gogland (1.0 Preview) 1.0 EAP
Build #GO-172.3968.45, built on September 5, 2017
Gogland EAP User
Expiration date: December 4, 2017
JRE: 1.8.0_152-release-915-b11 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.6
How can I fix this problem so that I can run go from the built in terminal in Gogland?
You've installed one Go version from one distribution and another Go version from another distribution (likely one from Homebrew and another from the distribution binaries, for example).
Either remove one or the other as your system is currently in an undefined state.
Gogland has nothing to do with this as it does not inject any parameters when you are using the terminal. You can run the file from Gogland itself by clicking on the green arrow next to func main() and it will use the internal logic to determine the execution model based on the SDK selected and the other parameters provided. You can customize the build process via Run | Edit Configurations.