From owner-freebsd-eclipse@FreeBSD.ORG Mon Oct 10 17:10:18 2005 Return-Path: X-Original-To: freebsd-eclipse@hub.freebsd.org Delivered-To: freebsd-eclipse@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B10FF16A41F for ; Mon, 10 Oct 2005 17:10:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8243B43D45 for ; Mon, 10 Oct 2005 17:10:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9AHAI0l010475 for ; Mon, 10 Oct 2005 17:10:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j9AHAIrU010474; Mon, 10 Oct 2005 17:10:18 GMT (envelope-from gnats) Date: Mon, 10 Oct 2005 17:10:18 GMT Message-Id: <200510101710.j9AHAIrU010474@freefall.freebsd.org> To: freebsd-eclipse@FreeBSD.org From: Herve Quiroz Cc: Subject: Re: ports/86860: [patch] Align java/eclipse invocation with javavmwrapper X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Herve Quiroz List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2005 17:10:18 -0000 The following reply was made to PR ports/86860; it has been noted by GNATS. From: Herve Quiroz To: Panagiotis Astithas Cc: bug-followup@FreeBSD.org Subject: Re: ports/86860: [patch] Align java/eclipse invocation with javavmwrapper Date: Mon, 10 Oct 2005 19:06:44 +0200 On Mon, Oct 10, 2005 at 06:23:28PM +0200, Herve Quiroz wrote: > Ok, I just realized that the launcher was not executing a 'java' command > but rather the original 'eclipse' executable so the fix may be more > complex than the one I submitted. > > I am currently installing eclipse then I will have a closer look at this > issue. After a bit of testing, it appears that the scenario I presented in my other message (JAVA_PREFERRED_PORTS=JAVA_PORT_NATIVE_BSDJAVA_JDK_1_1) will indeed break things. And that the fix I submitted does address this problem. Herve