Hello,
As some of you on this list know, I have been tinkering with a variety of
JDK's on FreeBSD in large part to get the Eclipse Platform running with any
sort of consistency. Over the course of a couple of weeks I have found the
following issues with each of the JDK's:
Native FreeBSD JDK 1.3.1
Under Eclipse, the native build of the 1.3.1 JDK refuses to allow the user to
commit a Java project to the file system. When the user attempts to create a
new project, the IDE responds with an error message that states that the
.project file (the metadata file used by Eclipse to track project changes) is
read only. This is the ONLY JDK where this problem is manifest.
Further, when using this JDK none of the local filesystems appear in the file
browser dialogs. In fact, as far as Eclipse is concerned the local file
system does not appear to exist at all.
Linux-SUN JDK 1.3.1
This is the only IDE I have been able to get to work with Eclipse with any
sort of consistency. The above problem does not exist and you can actually
open the help brower, perform automatic software updates over the web, etc.
Also, certain plugins that I have added to the environment (JBoss, Weblogic
integration work fine).
Linux-Sun JDK 1.4.1
This one is the most problematic and inconsistent of the bunch. While the
read only problem does not exist, any access of the help system, software
management etc brings the IDE to a crashing halt. Similarly, this JDK is dog
slow. Certain actions with the above JDK's can be performed in half the time.
Also, while the above JDK's only start one instance of the VM to run eclipse,
the 1.4.1 JDK causes no less than 10-12 instances of the VM to start.
Also, JBoss 3.0.0 crashes upon startup when using this JDK.
I have seen similar types of behavior with a variety of Java based
applications on FreeBSD. Most notably is JEdit when used in conjunction with
the native JDK. JEdit crashes due to file system errors.
Needless to say this is a bewildering set of problems. I have a notion that
the behavior with the native JDK has something to do with the Java security
policy. At the very least the evident discrepancies across the aforementioned
JDK's definitely give one cause for concern.
One other issue that I just don't understand is with the Linux compatibility
libraries. On both the native FreeBSD and 1.4.1 JDK Eclipse specifically
needs either the LD_LIBRARY_PATH variable to be set, or ldconfig -m
/compat/linux/lib to be run to start at all. However, with the Linux-Sun JDK
1.3.1 this is NOT NECESSARY. I just don't get it?
I am not really sure if this is the right forum to post this message, it may
very be more appropriate for the ports list. Any advice on these issues would
be appreciated. I was also wondering if there was a specific mailing list
dedicated to Java running on FreeBSD? This might be a good idea in order to
reduce traffic on questions.
I am running 4.7 with the Linux 7.1_1 base.
Regards,
Weston
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
