0

I have been developing my application in the Oracle JDK 1.6 development environment. When I move it to a different environment the code started getting broken, until I figured out the culprit was the environment was configured to OpenJDK 1.6.

After I installed Oracle JDK 1.6 in the second environment everything looks alright. Out of curiosity, how does the same Java version implementation have this effect? Aren't these implementations for the same specification?

TT.
  • 15,774
  • 6
  • 47
  • 88
Yohannes Gebremariam
  • 2,225
  • 3
  • 17
  • 23
  • 1
    Without more detail on how the code broke it's impossible to tell. – biziclop Jan 26 '16 at 18:56
  • 1
    Assuming that both are exactly the same, is incorrect. This may help to answer your question: [http://stackoverflow.com/questions/22358071/differences-between-oracle-jdk-and-open-jdk-and-garbage-collection](http://stackoverflow.com/questions/22358071/differences-between-oracle-jdk-and-open-jdk-and-garbage-collection) – Armaiti Jan 26 '16 at 18:58
  • 1
    Why are you using JDK 1.6, it's been EOL for several years now. It has known bugs and problems that won't ever be fixed, especially in the graphics/windowing API's. – SnakeDoc Jan 26 '16 at 19:14
  • Well I can't change that, It is a default in the company I am working on – Yohannes Gebremariam Jan 26 '16 at 19:22
  • In fairness to Yohannes, I am forced to use Java 6 at work, because of the code base's dependency on some library (not sure which one) which only works in 6. It's disgusting, but I'm not in a position to change it. – VGR Jan 26 '16 at 22:11
  • @YohannesGebremariam - Tell us the company name so that we can short-sell their stocks :-) – Stephen C Jan 26 '16 at 22:40
  • @VGR there is no reason a j6 library won't work on a j7 or j8 system. That's one of the main selling points of the java ecosystem... in fact, where I work, we have some jar libs that were compiled back for j5 and we still use them just fine in our j7 and j8 environments. – SnakeDoc Jan 27 '16 at 18:52
  • @SnakeDoc Unless, of course, that library uses sun.\* or com.\* classes that don't exist in later versions. Yes, it's a terrible practice. They do it anyway. – VGR Jan 27 '16 at 20:32

0 Answers0