View Single Post
  #6   (View Single Post)  
Old 17th May 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by SunSpyda View Post
I saw 1.7... wouldn't Netbeans work work this?
I don't use NetBeans, but I would assume yes. I highly doubt that NetBeans is rewritten with the release of each version of the JDK, & it would not surprise me that portions exist which rely on older editions of the JDK. In fact, if you were to build JDK 1.7, it requires JDK 1.5 as a dependency. The point here is that Sun imports legacy code in all JDK's. It is only due to licensing issues that 1.7 is available as a standalone package.

From a software development standpoint, it doesn't make sense to continually rewrite everything from scratch.
Quote:
If I got 1.7 off the package system, then separately installed Netbeans, is it a possibility it would detect Java SE 1.7, and work with it, yet not require 1.5, because I installed them independently?
The information I quoted is from -current. There is no picking & choosing of JDK versions. NetBeans has a run-time dependency upon JDK 1.5.
Quote:
If not, could I update to a bleeding edge version of Netbeans that might support 1.7?
It appears that you are making the assumption that dependency implies compatibility. The two are not necessarily related. I have no reason to believe that NetBeans cannot be used with JDK 1.7.
Quote:
I looked at Eclipse, but it didn't say what version of Java SE is required.
Again, print-run-depends on -current states the following:
Code:
This port requires package(s) "hicolor-icon-theme-0.10p4 javaPathHelper-0.3 jpeg-6bp4 tiff-3.8.2p3 glitz-0.5.6p1 jasper-1.900.1p0 libiconv-1.13 openmotif-2.3.0p0 jdk-1.5.0.16p0 gettext-0.17p0 sqlite3-3.6.13p0 pcre-7.9 glib2-2.18.4p3 atk-1.24.0 desktop-file-utils-0.15 png-1.2.35 cairo-1.8.6p1 pango-1.22.4p0 gtk+2-2.14.7p0 swt-3.2.2p1 nspr-4.7.3p0 nss-3.12p0 xulrunner-1.8.1.19p1 swt-browser-3.2.2p0" to run.
So to answer your question, running Eclipse will require compilation of JDK 1.5 as well.

It is unfortunate that licensing issues have added a cumbersome element to installing & configuring Java on OpenBSD, but that is the way that it is. In the future, this will become less of an issue -- assuming that the licensing stays as it is now.

Last edited by ocicat; 17th May 2009 at 08:24 PM.
Reply With Quote