[PATCH] Javavmwrapper defaulting to bsd.java.mk wrong?

[Tommy Pham]

--- Ulf Lilleengen <lulf at FreeBSD.org> wrote:

> Hello,
> 
> As I was trying to use jdk16 and diablo-jdk15 on the same machine, it
> would
> always default to jdk15. I figured the javavmwrapper script tries to
> use the
> bsd.java.mk PREFERRED_VERSION to determine this. This lead me to
> question if
> there is any good reason that bsd.java.mk should be checked before
> the
> versions set in javavms?
> 
> Attached is a patch which adds "support" for Java 1.6 to the wrapper
> script,
> but also changes the order in how the java version to be used is. I'm
> no big
> user of java, so I'm not sure if there is a reason for the old
> behaviour, so
> excuse me if this is wrong.
> 
> -- 
> Ulf Lilleengen
> 

Hi,

I did had this problem too at one point then I comment out the
diablo-jdk1.5 in /usr/local/java/javavms like this:

/usr/local/jdk1.5.0/bin/java # FREEBSD-JDK1.5.0
# /usr/local/diablo-jdk1.5.0/bin/java # DiabloCaffe1.5.0

There after I install a port requiring java like maven, I see it finds
===>  Installing for maven-1.0.2_1
===>   maven-1.0.2_1 depends on executable: java - found
===>   maven-1.0.2_1 depends on file: /usr/local/jdk1.5.0/bin/java -
found
===>   Generating temporary packing list

Where as before, it always refer to diablo jdk. I don't know if this is
causing any issues for other java apps but glassfish runs good for me
to certain extent :)

Hope this helps,
Tommy