From owner-freebsd-java@FreeBSD.ORG Tue Apr 5 16:31:52 2005 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EACF916A4CE for ; Tue, 5 Apr 2005 16:31:52 +0000 (GMT) Received: from arabica.esil.univ-mrs.fr (arabica.esil.univ-mrs.fr [139.124.41.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BCC043D1F for ; Tue, 5 Apr 2005 16:31:51 +0000 (GMT) (envelope-from herve.quiroz@esil.univ-mrs.fr) Received: from arabica.esil.univ-mrs.fr (localhost [127.0.0.1]) j35GVTtG077650; Tue, 5 Apr 2005 18:31:29 +0200 (CEST) (envelope-from herve.quiroz@esil.univ-mrs.fr) Received: (from rv@localhost) by arabica.esil.univ-mrs.fr (8.13.3/8.13.3/Submit) id j35GVQn0077649; Tue, 5 Apr 2005 18:31:26 +0200 (CEST) (envelope-from herve.quiroz@esil.univ-mrs.fr) X-Authentication-Warning: arabica.esil.univ-mrs.fr: rv set sender to herve.quiroz@esil.univ-mrs.fr using -f Date: Tue, 5 Apr 2005 18:31:26 +0200 From: Herve Quiroz To: Greg Lewis Message-ID: <20050405163126.GA77275@arabica.esil.univ-mrs.fr> Mail-Followup-To: Greg Lewis , Sam Lawrance , java@FreeBSD.org References: <1112706453.750.22.camel@dirk.no.domain> <20050405133205.GA63174@arabica.esil.univ-mrs.fr> <20050405154408.GA443@misty.eyesbeyond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050405154408.GA443@misty.eyesbeyond.com> User-Agent: Mutt/1.4.2.1i cc: java@FreeBSD.org cc: Sam Lawrance Subject: Re: JDK specific classpaths X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 16:31:53 -0000 Hi Greg, On Tue, Apr 05, 2005 at 09:44:08AM -0600, Greg Lewis wrote: > On Tue, Apr 05, 2005 at 03:32:05PM +0200, Herve Quiroz wrote: > > On Tue, Apr 05, 2005 at 11:07:32PM +1000, Sam Lawrance wrote: > > That said, and until some volunteer starts working on improving > > javavmwrapper, I would go with method #2 (overridable JAVA_HOME). > > The problem is that although javavmwrapper exports JAVA_HOME to its > children, we're wanting to use JAVA_HOME during its invocation. > > While I don't think a full blown tool to print out JAVA_HOME is > necessarily warranted, it may be useful to have javavmwrapper do > some substitutions on the command line arguments it is given, e.g. > "s/%%JAVA_HOME%%/${JAVA_HOME}" in this particular case. Presently > I can only see uses for JAVA_HOME and the version, so this should > be quite simple to implement. I agree with you here. I had already thought that a JAVA_HOME print out tool would have been useful for Ant, which requires JAVA_HOME so that it may find core classes and tools. It has to discover a suitable JAVA_HOME (or verify the one specified by the user) first, and then run ${JAVA_HOME}/bin/java. And now that you refreshed my memory regarding the logic in javavmwrapper (already exporting JAVA_HOME to its children), I think we may already greatly simplify or improve this launcher shell script. Thanks for reminding me of this, Greg. :) BTW, Sam sent me a patch using the method #2 (overridable JAVA_HOME) I suggested so I guess we are fine for now regarding NetRexx/JAVA_HOME. OTOH, looking at '/usr/local/bin/maven': TOOLS_JAR="${JAVA_HOME}/lib/tools.jar" So that's another use case for the %%JAVA_HOME%% feature you suggested. Now we have to decide whether it's worth implementing the feature. But I think we need to find out exactly the ports that would benefit from such feature... Herve