From owner-freebsd-ports  Fri May  4  7:30: 8 2001
Delivered-To: freebsd-ports@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 4811B37B423
	for <freebsd-ports@hub.freebsd.org>; Fri,  4 May 2001 07:30:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f44EU2L23781;
	Fri, 4 May 2001 07:30:02 -0700 (PDT)
	(envelope-from gnats)
Received: from heinz.jollem.com (c104187.upc-c.chello.nl [212.187.104.187])
	by hub.freebsd.org (Postfix) with ESMTP id D1FF337B422
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  4 May 2001 07:20:15 -0700 (PDT)
	(envelope-from ernst@heinz.jollem.com)
Received: (from ernst@localhost)
	by heinz.jollem.com (8.11.3/8.11.3) id f44EIZv88301;
	Fri, 4 May 2001 16:18:35 +0200 (CEST)
	(envelope-from ernst)
Message-Id: <200105041418.f44EIZv88301@heinz.jollem.com>
Date: Fri, 4 May 2001 16:18:35 +0200 (CEST)
From: Ernst de Haan <ernst@heinz.jollem.com>
Reply-To: ernst@heinz.jollem.com
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.113
Subject: ports/27079: Improvements for javavmwrapper?
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         27079
>Category:       ports
>Synopsis:       Improvements for javavmwrapper?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 04 07:30:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Ernst de Haan
>Release:        FreeBSD 4.3-RELEASE i386
>Organization:
Jollem Information Technology
>Environment:
System: FreeBSD heinz.jollem.com 4.3-RELEASE FreeBSD 4.3-RELEASE #3: Mon Apr 30 08:56:44 CEST 2001 root@heinz.jollem.com:/usr/src/sys/compile/HEINZ i386


	
>Description:
As I expressed before, I really like the concept of javavmwrapper, but I'm still struggling to make effective use of it. When I install a JDK from the ports, the javavmwrapper port is installed as well. This allows me to use multiple Java VMs and to switch between them. The 'current' Java runtime can be called using 'javavm'. Problem is that most programs that use Java expect the command 'java' to point to the Java runtime, 'javac' to the Java compiler and 'javadoc' to the Javadoc documentation generation tool (to name a few). And they also expect the JAVA_HOME environment variable to have a sensible value. The javavmwrapper system still doesn't provide this level of transparency.
>How-To-Repeat:
Install a JDK. Run 'javac' or 'javadoc' or 'javah' after that.
>Fix:
My suggestion: Make sure that none of the JDKs install a 'java', 'javah', 'javadoc' (etc) executable in /usr/local/bin/ but make javavmwrapper install these in /usr/local/bin/. They may all be symlinks to the same shell script. Now make sure these scripts work as expected, similar to the current 'javavm' shell script, written by Maxim Sobolev.
If this idea is appreciated, *and* if Maxim would like me to, then I could have a look at this and try to come up with a first attempt to implement this approach.
>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message