Date: Sat, 28 Jan 2006 16:54:18 +0100 From: Alex Kiesel <alex@kiesel.name> To: Panagiotis Astithas <past@ebs.gr> Cc: freebsd-java@freebsd.org Subject: Re: JBoss 4.0.* does not build (sometimes?) Message-ID: <1138463658.689.3.camel@boost.home.ahk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1138463658.689.3.camel>