atom feed13 messages in org.freebsd.freebsd-javajdk14 port usable for development?
FromSent OnAttachments
Mike HardingJul 21, 2003 8:39 am 
Michael E. MercerJul 21, 2003 8:42 am 
Nick JohnsonJul 21, 2003 8:52 am 
Dag-Erling SmørgravJul 21, 2003 1:10 pm 
Ernst de HaanJul 21, 2003 11:59 pm 
Dag-Erling SmørgravJul 22, 2003 12:40 am 
Jonathan ChenJul 22, 2003 2:49 am 
Mike HardingJul 22, 2003 8:44 am 
Ernst de HaanJul 22, 2003 8:49 am 
Joe ShevlandJul 22, 2003 5:12 pm 
Tom SamploniusJul 22, 2003 11:33 pm 
Ernst de HaanJul 23, 2003 12:37 am 
Joe ShevlandJul 23, 2003 7:03 pm 
Subject:jdk14 port usable for development?
From:Joe Shevland (jshe@ozemail.com.au)
Date:Jul 23, 2003 7:03:07 pm
List:org.freebsd.freebsd-java

My apologies, I'm running patchset 3; my other piece of bad|misinformation is reporting a problem with keytool itself ... I later thought this is written in C/C++ and doesn't call into any JVM stuff, so its probably not an interesting report.

I did remove CPUTYPE from /etc/make.conf a while back, I'm not sure if that has made any difference, but it may well interact with JSSE/OpenSSL stuff I suppose.

I'm going to concentrate our testing more and more on BSD now, so hopefully I can lend a hand with the port now I've got a bit more time. I'm also using the Server hotspot VM (well, I'm setting the -server flag at least).

Regards,

-----Original Message----- From: Tom Samplonius [mailto:to@sdf.com] Sent: Wednesday, 23 July 2003 2:41 PM To: Joe Shevland Cc: ja@freebsd.org Subject: Re: jdk14 port usable for development?

On Wed, 23 Jul 2003, Joe Shevland wrote:

...

Its working fine with the native JDK 1.4.1 in all areas, but keytool appears to be taking a long time... I did have some lock-ups using JSSE, but I haven't seen those in a while and they may be prior

to patchset 8. ...

I thought the jdk 1.4.1 patchset was only up to patch 3, but the jdk 1.3.1 patchset was up to patch8?