Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I have couple of projects using JDK 1.8 in production. However Java is paid from January 2019 onwards. Is my problem solved if I migrate my projects to OpenJDK 1.8 because it's open source?
As far as I know, it concerns only the Oracle Java APIs.
OpenJDK and OpenJFX are largely independent (besides getting contributions from Oracle).
As general Oracle Java was a bit smarter than the OpenJDK (on Linux), the entire outcries are a storm in a glass of water: it makes a (ill guided) sense to let Oracle be paid for its development effort.
The thing to do, is trying out the OpenJDK, and taking notion of com.sun classes.
You might need to look for new versions of your typical server or framework, that might rely on com.sun.* classes.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am refering to the link
Public updates for Oracle Java SE 8 released after January 2019 will not be available for business, commercial or production use without a commercial license.
Java is Open Source for sure, maybe The Community will release OpenJDKs updates, but i still have my worries about this news...
I really would like to know about your opinions, and if we imagine the worst case (wich i do not hope), that Oracle do the same with the others new java versions...
What are the solutions ?
The link you are referring to looks to me like a normal Java version lifecycle announcement. Each version of Java SE eventually stops receiving public updates, and by that time, there is a newer Java SE in wide use.
See Oracle Java SE Support Roadmap and Java version history.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
When I was first learning java from a crash course, we were advised by the teacher to change the jdk after long use.
While she couldn't provide any scientific explanation to this, even I find it necessary to change the jdk at points of time. In the computer at my home, sometimes it happens that a program that I've written, is syntactically, semantically and logically correct, but both BlueJ and NetBeans give unexplained compilation or run-time error. Both BlueJ and NetBeans run on the same jdk.
If I download a new jdk package and install it, removing the previous one, it solves the problem.
Can anyone explain this?
New versions of the JDK can run old code, but the opposite is not necessarily true: Recent applications will take advantage of recent features of the JDK, and will not be compatible with older versions.
Note that sometimes, applications built with some JDK may not run with newer versions. For instance, JDK 7 has removed some deprecated classes from JDK1.6.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
I've upgrade my Java JDK installation to a later minor release version (e.g. 1.8.131 to 1.8.144).
Should I recompile project source code to get any security benefits from bytecode generation or should I just run the old bytecode on the updated JRE?
Any real world examples welcome as I will need to justify this to the project team.
You are mistaken.
The java compiler doesn't do much, besides turning Java source into bytecode. There are few special optimisations. And no "security" related things at all.
And keep in mind: all invokations of system methods that your code is doing - will be going to Java8 classes on a Java8 VM.
Thus there is no pressing reason to update "everything".
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was wondering why Java doesn't have a REPL. Is there some technical limitation? As an aside, how do REPLs actually work, what's going on with say the Scala REPL?
I think they are planning/thinking to introduce REPL in java 9. One of the problem according to Scala author Odersky is that REPL are expression-oriented and java on the other hand is statement-oriented, so not much so much useful for Java.
The IBM VisualAge for Java IDE had a REPL (or more precisely, a Smalltalk-style "Worksheet"), by virtue of it being written in Smalltalk and basically only a slightly modified version of the IBM VisualAge for Smalltalk IDE. However, when IBM VisualAge for Java was rewritten in Java and released under the name of IBM VisualAge for Java Micro Edition, it still kept its REPL.
And when IBM modularized IBM VisualAge for Java Micro Edition and released it as Open Source under its new name "Eclipse", it still kept its REPL, and it is in fact still there in the very latest version, under the name "Scrapbook page".
That one is not the only one, there are other REPLs as well, e.g. the REPL behind http://JavaREPL.Com/ is Open Source on GitHub.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I am using applet code in my application. When I am running that applet it is aksing me to install java 7 version.
Is it mandatory to install java7 version?
If it is mandatory how the applets were run in java6 version previously?
I am confused.
Is it mandatory to install java7 version.
Basically, yes. And you should do it anyway, since Java 6 is no longer getting security patches.
If it is mandatory how the applets were run in java6 version previously.
The author has (presumably) changed something. He/she might have started using Java 7 language constructs or Java 7 specific library APIs. Or he/she might have just changed the JNLP configurations to force you to upgrade for your own good.