I've a new computer with Debian 9 / 64bits.
After installing Netbeans 8.2 and Codename Plugin 5.0 if i try to open "CodenameOne Settings" or "CodenameOne Designer" nothing happens.
I've checked JRE_JAVA and JDK_JAVA and PATH environment variables and them points to the correct path.
I don't see any error message but the tools dont start.
I dont know what happens but i remember a similar issue in the old computer with Debian 6 / 32bits.
Can anybody help me?
Thanks a lot
Ramon Garcia
The default version of Java on Linux systems is OpenJDK which is a bit problematic due to its lack of JavaFX support. With newer JDKs we updated Codename One to download JavaFX dynamically as it was removed from the JDK but since the dynamic download only works with JDK 10 or newer (due to the way the people at Oracle compiled JavaFX) this would be the minimum version of OpenJDK.
So you can either install Oracle JDK 8 or Open JDK 11 to keep compatibility.
Notice you can track this issue by running the designer/gui builder from the command line and seeing the point of failure: https://www.codenameone.com/blog/tip-track-designer-guibuilder-issues.html
Related
I have troubles installing Cytoscape.
All started from the common "The JVM could not be started" error. Hence, I downloaded the debugging "Windows.bat" script that yielded the following results :
Cytoscape System Requirements Checker for Windows
Target Cytoscape version: 3.7.2
Your Windows version is:
Microsoft Windows [version 10.0.18362.720]
Java is installed
Your system is 64 bit
Your JAVA_HOME is set to C:\Program Files\Java\jdk-14
Your Java version is at least version 8 as required
Your Java version is no higher than version 8 as required
Your Java is 64 bit as recommended
Problem: The "app" store at apps.cytoscape.org is not reachable with a timeout of 30000ms
Summary
Your system has some issues.
Please fix those and re-run this script again:
- App store at apps.cytoscape.org is not reachable
Then, it tries to determine the itinerary but stops around the 17-18 step.
Thanks a lot for your time !
Actually, you have a different problem... Cytoscape 3.7.2 is only supported on Java 8, and you have Java 14 installed. Cytoscape 3.8 (release is imminent) will support Java 11, but not Java 14. Getting the correct Java installed should allow you to run Cytoscape. The app store problem might be transitory. I would suggest trying Cytoscape 3.8 before going too far out of your way to try to debug this. We intend to release Cytoscape 3.8 today or tomorrow...
-- scooter
I have installed IBM JDK 7 with release 1 and i am try to run Hello world program with -Xmt option on Ubuntu 14(OS installed in Virtual Box), but runtime i got Command-line option not recognized: -Xmt.
[In IBM documentation they said to create tenant use -Xmt with java command.]
These features are no longer available in their latest release thats why.
Check the links: here and here
They say that the had some issues but the thing is they also removed it from the developers preview page so there is no way to actually test it.
I have Mac OS X 10.9 and Java SE Runtime Environment (build 1.7.0_17-b02)... I had another version of JEdit (I guess JEdit 4) and Java 6 before and my JEdit was working fine.
Then I upgraded Java to Java 7 because NetBeans7.4 needed to be installed with Java 7 (and I needed this new NetBeans because I had a fatal issue with NetBeans 7.3.1). So anyway, I installed Java 7 and I installed NetBeans 7.4 and my netbeans is working perfectly now, but when I tried to run the JEdit it brought up an alert saying it needs Java SE 6 to run!
I did some search in the net, and it seems that JEdit 4.5 (and I guess JEdit 5.1 too!) should not have any issue with Java 7, So I installed JEdit 5.1.0... I expected that it should work and don't bring up that complain alert BUT it didn't work and brought up "Java SE 6 is needed" complain again ...
I still can run JEdit using this command, but I can't use Cmd+C & Cmd+V shortcuts for copy and paste and it kills me!
java -jar /Applications/jEdit.app/Contents/Resources/Java/jedit.jar
Is there anybody who knows why JEdit 5.1 is complaining about Java 6 and how to fix it?! I really appreciate your help!
https://sourceforge.net/tracker/?func=detail&aid=3615181&group_id=588&atid=100588
After almost 3 months struggling with jEdit I'm ready to give up... I still can't run jEdit like a normal app. What do you suggest to replace my jEdit?! The main feature I need is realtime access to the server files... Most of editors keep a local version of files, so they don't show the changes when they are made in the server side. for example when I switch to a new git branch on server, my netbeans is still showing the branch that I was working before switching, so I need to do a complete download on the project. Any idea?!
#Monica About one year later after your question, I've experienced the same issue with Mountain Lion (according to jEdit's homepage, 5.1.0 is still the current stable version).
I've installed jEdit in /Applications/Dev/ (not /Applications as most people do, I believe; that's not important except for designating the path, see below). I'm using Java 7.
The following works for me from the command line, like for you:
java -jar /Applications/Dev/jEdit.app/Contents/Resources/Java/jedit.jar
So, I used Automator to create a normal MacOS Application named "MyJEdit.app" as in the screenshot. Now I can launch MyJEdit instead of jEdit. Other java flags might be required, for instance to set the memory usage (cf java -help and java -X).
jEdit on Mac OS X and Java 7 is a long story of annoyances, and fine points that Apple did not get quite right up to Java 6, and Oracle still learning about native platform support in the past 1-2 years.
Starting with Jdk-7u40 it works technically quite well, even Retina displays, but jEdit needs to be adapted slightly.
jEdit 5.2 will probably work with Java 7 out of the box, but a few points are still open. See also the tracker item 3615000 at Sourceforge.
Here is a practical proof that it works: Isabelle/jEdit -- it is an application based on jEdit that is bundled differently than official jEdit 5.1.0.
I would like to install ColdFusion Builder 2 Update 1 as a Plug-in for Eclipse 4.3.
The install seems to work without errors but when I attempt to register my license code, I get an error dialog box that says:
"The chosen operation is not enabled."
None of the CFB features appear in Eclipse.
In some of the documentation that I've found it references installing to Eclipse 3.6.
Can CFB 2u1 get installed on Eclipse 4.3? If not, does someone know which version of Eclipse to use for CFB? Hopefully it is something recent or I'm doing something wrong for the install.
I don't know if it matters, but I'm running:
Windows 7 Pro 64-bit
16GB RAM
According to the ColdFusion Builder System Requirements page one needs Eclipse 3.7.1. Having tried to install it on versions later than that, failing, and talking to Adobe about it, they confirmed that one needs that precise version. More recent ones won't do. This is a bit subpar on the part of Adobe, but so be it.
A while back I released an application in Java. While I targetted it for Java 6, I realized that there was a significant Macintosh user base. At the time, Apple had not gotten around to creating a JRE 6 for their users, so I had to make the application compatible with both Java 5 and 6.
Now I've returned to that project and realize that I can't support those users any more; Sun won't let me download the JDK 5 anymore because it's end of life. So I'm caught at a crossroads; as far as I can tell, PPC Mac users still don't have a JRE 6 to use.
So I ask this question: How do I resolve this predicament? I still want to support those users, but I simply don't have a JDK with which to build. Has Apple released a JRE 6 for their PPC users? Is there an alternate way to get JDK 5 (other than becoming a business member of Sun)? Is there some alternative recommendation to supporting these users?
Regards,
-- Shirik
EDIT: Some additional info, if Apple has released Java 6 for PPC, how easy is it to get? I ask this because I'm still constantly seeing logs from my users which indicate PPC architecture with a Java 5 VM.
You could use -target 1.5 -source 1.5 with your Java 6 JDK, to generate 1.5-compatible class files.
You can download Java 5 from Sun. You just have to look in the right place.
http://java.sun.com/javase/downloads/previous.jsp - J2SE 5.0, 1.4.2, 1.3.1
http://java.sun.com/products/archive/ - all releases going back to JDK 1.1
Note that these are all existing public releases. The material you got from Sun would have said there would be no new public releases of Java 5.0. They were pointing out that if you needed patches for recently discovered security issues and other bug fixes for Java 5.0 etc, you would have to pay for them.
Obviously, JDKs for Apple platforms are not available from Sun, but this is nothing to do with the fact that Sun have "end-of-lifed" Java 5.0. The fact is that they have never been available from Sun ...
Having said that, in the long term you need to be able to migrate your application to Java 6.0, 7.0 (due out later this year) and so on. At some point you are going to have to draw the line and say "sorry ... no more updates" for the shrinking number of users with old PPC and 32-bit Intel Macs.
As far as I know, Apple has only released Java 6 for x86-64, and I'd be willing to bet my hat that they will never release Java 6 for either PPC or for plain old 32-bit x86 (note that every Mac released after about mid-2007 or so is x86-64).
Soylatte might work (I have not tried it myself).
If you want to support older platforms, including PowerPC macs, it is a good idea to write code that can run on older Java releases. These days Java 5 is a relatively safe bet, but you may want to go even further and e.g. use retroweaver to generate Java 1.4.
You can download a version of the OpenJDK 1.7 from intricatesoftware.com
it is, unfortunately, a headless build of the JDK; i.e., can't open a display, and hence can't use to run IntelliJ, but Eclipse runs on it just fine.
I'm running it on 10.5.8, on a PPC ("cheese grater",) with Eclipse 4.3.2 / Kepler, and it all seems to work fine. :-)
(though, in honesty, a new configuration on the box, so we'll see how it goes over time)