JBoss 4.0.* does not build (sometimes?)
past at ebs.gr
Mon Jan 30 01:53:09 PST 2006
Alex Kiesel wrote:
> 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?
This behavior is unusual in the ports tree, AFAIK. Libraries should be
installed in $JAVAJARDIR (see bsd.java.mk). I think you should file a PR
about this behavior of the axis port.
More information about the freebsd-java