Date: Thu, 10 Oct 2002 12:41:27 +0000 From: "Weston M. Price" <wmprice@direcway.com> To: freebsd-questions@freebsd.org Subject: Native JDK 1.3.1 Linux JDK 1.3.1 vs JDK 1.4.1 inconsistencies Message-ID: <200210101241.27653.wmprice@direcway.com>
next in thread | raw e-mail | index | archive | help
Hello, =09As some of you on this list know, I have been tinkering with a variety= of=20 JDK's on FreeBSD in large part to get the Eclipse Platform running with a= ny=20 sort of consistency. Over the course of a couple of weeks I have found th= e=20 following issues with each of the JDK's: Native FreeBSD JDK 1.3.1 =09Under Eclipse, the native build of the 1.3.1 JDK refuses to allow the = user to=20 commit a Java project to the file system. When the user attempts to creat= e a=20 new project, the IDE responds with an error message that states that the=20 =2Eproject file (the metadata file used by Eclipse to track project chang= es) is=20 read only. This is the ONLY JDK where this problem is manifest.=20 =09Further, when using this JDK none of the local filesystems appear in t= he file=20 browser dialogs. In fact, as far as Eclipse is concerned the local file=20 system does not appear to exist at all. =09 Linux-SUN JDK 1.3.1 =09This is the only IDE I have been able to get to work with Eclipse with= any=20 sort of consistency. The above problem does not exist and you can actuall= y=20 open the help brower, perform automatic software updates over the web, et= c.=20 Also, certain plugins that I have added to the environment (JBoss, Weblog= ic=20 integration work fine).=20 Linux-Sun JDK 1.4.1 =09This one is the most problematic and inconsistent of the bunch. While = the=20 read only problem does not exist, any access of the help system, software= =20 management etc brings the IDE to a crashing halt. Similarly, this JDK is = dog=20 slow. Certain actions with the above JDK's can be performed in half the t= ime.=20 Also, while the above JDK's only start one instance of the VM to run ecli= pse,=20 the 1.4.1 JDK causes no less than 10-12 instances of the VM to start.=20 =09Also, JBoss 3.0.0 crashes upon startup when using this JDK.=20 =09I have seen similar types of behavior with a variety of Java based=20 applications on FreeBSD. Most notably is JEdit when used in conjunction w= ith=20 the native JDK. JEdit crashes due to file system errors.=20 =09Needless to say this is a bewildering set of problems. I have a notion= that=20 the behavior with the native JDK has something to do with the Java securi= ty=20 policy. At the very least the evident discrepancies across the aforementi= oned=20 JDK's definitely give one cause for concern.=20 =09One other issue that I just don't understand is with the Linux compati= bility=20 libraries. On both the native FreeBSD and 1.4.1 JDK Eclipse specifically=20 needs either the LD_LIBRARY_PATH variable to be set, or ldconfig -m=20 /compat/linux/lib to be run to start at all. However, with the Linux-Sun = JDK=20 1.3.1 this is NOT NECESSARY. I just don't get it????? =09I am not really sure if this is the right forum to post this message, = it may=20 very be more appropriate for the ports list. Any advice on these issues w= ould=20 be appreciated. I was also wondering if there was a specific mailing list= =20 dedicated to Java running on FreeBSD? This might be a good idea in order = to=20 reduce traffic on questions. I am running 4.7 with the Linux 7.1_1 base.=20 Regards, Weston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210101241.27653.wmprice>