Bug#445006: maven2: Selects first JRE found, ignoring alternatives

[Krzysztof Sobolewski]

Package: maven2
Version: 2.0.7-1
Severity: normal

I have two Java packages installed: sun-java5-jre and sun-java6-jre.
The latter is selected as /usr/bin/java by update-java-alternatives.
Now when Maven starts, it tries to select $JAVA_HOME by looking
into places where it might find Java (/usr/lib/jvm), apparently giving priority
to Sun packages. Unfortunately, in my case, it selects java-1.5.0-sun,
because it comes up first. This is mostly fine, but creates problems when,
for example, I'm compiling a program that uses newer APIs.

The start script should probably first try to determine where
/usr/bin/java (or even `which java`) comes from.


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-ck1 (PREEMPT)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages maven2 depends on:
ii  libcommons-cli-java      1.0-8           API for working with the command l
ii  libdoxia-java            1.0-alpha-7-1   a powerful content generation fram
ii  libjsch-java             0.1.34ds1-1     java secure channel
ii  libjtidy-java            7+svn20070309-1 a Java port of HTML Tidy, a HTML s
ii  libplexus-interactivity- 1.0-alpha-6-2   interactivity API for the Plexus f
ii  libwagon-java            1.0-beta-2-1    tools to manage Maven artifacts an
ii  libxalan2-java           2.7.0-5         XSL Transformations (XSLT) process

maven2 recommends no packages.

-- no debconf information

----------------------------------------------------------------------
Pokaz innym kto tu rzadzi!
Kliknij >>> http://link.interia.pl/f1bbc