From owner-freebsd-java@FreeBSD.ORG Wed Oct 3 06:31:36 2007 Return-Path: Delivered-To: freebsd-java@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9502E16A417 for ; Wed, 3 Oct 2007 06:31:36 +0000 (UTC) (envelope-from mark.evenson@gmx.at) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id E9FE113C45B for ; Wed, 3 Oct 2007 06:31:35 +0000 (UTC) (envelope-from mark.evenson@gmx.at) Received: (qmail invoked by alias); 03 Oct 2007 06:24:54 -0000 Received: from colo-69-31-82-90.pilosoft.com (EHLO [IPv6:::1]) [69.31.82.90] by mail.gmx.net (mp035) with SMTP; 03 Oct 2007 08:24:54 +0200 X-Authenticated: #32963322 X-Provags-ID: V01U2FsdGVkX1+Yof53jcmYcRfdBKJxHw7AgJj0N66r7YraIkgN7I +mujOoPmLvzvwJ Message-ID: <470335B2.2060109@gmx.at> Date: Wed, 03 Oct 2007 08:24:50 +0200 From: Mark Evenson User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 Newsgroups: gmane.os.freebsd.devel.java To: Michael Conlen References: <20071001100936.GA10202@rv-laptop> <20071002211357.GA48667@misty.eyesbeyond.com> <4A6D516D-0C49-478B-8060-83EC012E6C29@obmail.net> In-Reply-To: <4A6D516D-0C49-478B-8060-83EC012E6C29@obmail.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-java@FreeBSD.org Subject: Re: Removal of Java 1.1 and 1.2 support in the ports tree X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2007 06:31:36 -0000 Michael Conlen wrote: [...] > > If someone needs it for this reason there's always the option of doing > what I do when I need to test compatibility with Windows 95, install a > virtual machine with the old version of FreeBSD on it to test with. It's not so much about testing compatibility: it's about generating the bytecode in the first place. The Sun jdk-1.1 compiler can produce some "interesting" bytecode that will pass the Microsoft VM verifier, whereas post-jdk-1.2 compilers producing classfiles that should be compatible (via the appropiate compiler switches, and making sure only classes that existed in jdk1.1 are referenced), are actually rejected. I never really tracked down the nature of the deviations, mainly because trying to figure out the behavior of the closed-source Microsoft VM seemed like a losing proposition. -- "[T]his is not a disentanglement from, but a progressive knotting into."