From owner-freebsd-java@FreeBSD.ORG Sat Jan 28 15:54:25 2006 Return-Path: X-Original-To: freebsd-java@freebsd.org 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 21F0816A420 for ; Sat, 28 Jan 2006 15:54:25 +0000 (GMT) (envelope-from alex@kiesel.name) Received: from xhantos.de (xhantos.de [82.165.42.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9DFE43D45 for ; Sat, 28 Jan 2006 15:54:24 +0000 (GMT) (envelope-from alex@kiesel.name) Received: from boost.home.ahk (p54A32EB3.dip0.t-ipconnect.de [84.163.46.179]) by xhantos.de (Postfix) with ESMTP id 70BFA9B418; Sat, 28 Jan 2006 16:55:33 +0100 (CET) From: Alex Kiesel To: Panagiotis Astithas In-Reply-To: <43D0C183.5050900@ebs.gr> References: <1137336063.713.4.camel@boost.home.ahk> <1137338926.713.8.camel@boost.home.ahk> <43D0C183.5050900@ebs.gr> Content-Type: text/plain Date: Sat, 28 Jan 2006 16:54:18 +0100 Message-Id: <1138463658.689.3.camel@boost.home.ahk> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-java@freebsd.org Subject: Re: JBoss 4.0.* does not build (sometimes?) 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: Sat, 28 Jan 2006 15:54:25 -0000 On Fri, 2006-01-20 at 12:54 +0200, Panagiotis Astithas wrote: > Alex Kiesel wrote: > > On Sun, 2006-01-15 at 15:41 +0100, Alex Kiesel wrote: > >> I do suspect, it's got nothing todo with the FreeBSD versions, but more > >> with something else, I do not see. Both machines only have this single > >> jdk installed - nothing else. > > > > It seems that suspiction was correct. I noticed that one the failing > > machine, the port axis-1.2.2 was installed while on the other it wasn't. > > > > After removal of the port, the compile went through. JBoss seems to ship > > an own version of Axis which was behind the port's version in the > > classpath probably. > > > > So, I wonder if java/jboss4 should list axis-* as CONFLICTS? > > A better solution would be to patch the build process to not reference > outside jars. I agree. I have tried to develop a patch for this, but yet have not come to a solution. The source of the problem is that Axis installs its jars in $JAVA_HOME/jre/lib/ext - thus they're in the default class path, if I get this right. How can I remove classes from that path? Should I file a pr for this, so that at least people hitting the same issue are able to find a reference about this? Regards, -Alex