I am trying to build a Cytoscape app using maven, and I am using EKZTAZI 5.0.1 . When I use Maven Package, it throws the following error :
Execution ekstazi of goal org.ekstazi:ekstazi-maven-plugin:5.0.1:select failed: Running with Java 9 requires -Djvm.options=jdk.attach.allowAttachSelf=true
I have tried searching on how to pass this option online but I am unsure on how to. Any help will be appreciated.
There is currently no Java 9 support available for the public release of Cytoscape, which is likely what is causing your issue.
The next major version release is in development and has Java 9 support (check the Cytoscape GitHub if you're interested in using this: https://github.com/cytoscape/cytoscape)
Related
Error: A JNI error has occurred, please check your installation and try again.
Eclipse states: test has been compiled by a more recent version of the Java Runtime (class file version 56.0), this version of the Java Runtime only recognizes class file versions up to 52.0.
I had the problem referenced at this question: "Could not find or load main class" while trying to use JavaFX in Eclipse When using JDK13 and JavaFX13. All solutions pointed to downgrading to Java 8.
I installed Java 8, updated the build path, and it built fine. But now I get the error I am using Eclipse 2019-06 (4.12.0), JavaFX13, and JDK 1.8.0_231.
I researched the answer but the two questions that come didn't help. One was for an IntellJ solution and the other had a package I am unfamiliar with, and the error had to do with that package.
I simply don't know how to correct the build path or dependencies to fix this issue. It appears I need a lower version of the JVM, but cannot seem to locate it. Am I right, or can you please help?
Well, I have dropped back to JDK 8 and the built in JavaFX. Despite my best efforts, I cannot get JDK13 and JavaFX 13 to work without receiving the error "Could not find or load main class" (see link in post). Since there is no solution to that problem yet that works for me, I can bypass my error on this request all together and just use much older packages.
When I try to make a maven clean install I get this errors:
I have looked for this error on other posts, and they say to use jdk instead of jre or that the path is bad, but none of those is my problem.
This project is Mule Aplication made with Anypoint Studio.
Thanks!!
From your output I can see you are using Java 11. Mule does not support java 11 yet.
Mule 4.2 will support Java 11 when released.
For now you need to use jdk 8.
https://support.mulesoft.com/s/article/Mule-Runtime-support-for-Java-11-FAQ
AFAIK App Engine supports all standard java libraries when project uses java 8. For some reason Intellij show this as an error. I can run local development server and deploy this project to app engine and it works ok.
I think I could just disable the check for forbidden code in App Engine but is there something else that would actually be forbidden with java 8 also.
Is this issue with gcloud plugin or intellij...?
Edit:
Added project structure
As per documentation The App Engine Java 8 runtime supports the standard public Java library, so there shouldn't be any limitations.
Ther has been an issue (#CrazyCoder's comment) opened in google-cloud-intellij library which has been resolved in the latest version.
IntelliJ Ultimate 2018.2 build on July 2018 solved the issue
Can anyone help me with this error message I'm getting from IntellIJ?
(I'm using Java 8 - the error is only occurring on a very small percentage of the classes)
[2014.05.06 10:14:39] (Coverage): Error during class instrumentation: xxx.yyyy: java.lang.IllegalArgumentException: INVOKESPECIAL/STATIC on interfaces require ASM 5
Thanks
Daniel
If you Google for that exception message, you will find that there are a small number of hits in a variety of code analysis tools. It seems to be a tool-chain compatibility issue. Java 8 code breaks various third party tools that use older versions of the ASM library.
You need to report this to the developer for the tool or plugin that is having problems.
I have been testing a patch from intellij which fixes the problem.
It will be released publicly in 13.1.3 EAP.
I am trying to install the Play! framework onto my OSX Mavericks laptop. Everything installs and works fine using the default install paths until I try to convert a new application to an eclipse project. I can convert Scala projects just fine. But when I try to convert a Java application to an eclipse project I get the following error from the Play! console:
[TestAppOne] $ eclipse
[info] About to create Eclipse project files for your project(s).
[info] Compiling 2 Scala sources and 1 Java source to /Users/mcd/play/TestAppOne/target/scala-2.10/classes...
[error] could not find scala-library.jar
[error] Use 'last' for the full log.
I can see the scala-library.jar (2.10.3) and I even added it to /etc/paths; no luck. I am using Java 1.7 and Kepler eclipse and Play 2.2.2-RC3. Any suggestions to help convert the Play! project to eclipse?
try to remove everything redundant from path, leave only java and play home (http://www.playframework.com/documentation/2.0/Installing) there and "replay" your project
Is there any particular reason that you are using RC instead of stable release?
Play 2.2.2-RC3 has reported issue about this problem 3 days ago, check on Github or similar question posted few hours ago on the StackOverflow
(FYI, just tested: sample Play 2.2.1 project eclipsied on Mavericks without any problem, unfortunately I have no Eclipse installed, but assume, that there should not be any problems to open it there, Idea works like a charm)