tags 445006 +pending
thanks
The fix I previously suggested for this bug would not work with
java-gcj, due to the different ways the Java packages are set up in the
alternatives system. E.g.
/usr/bin/java -> /etc/alternatives/java ->
/usr/lib/jvm/java-1.5.0-sun/jre/bin/java
/usr/bin/java -> /
Hello,
On Sun, Oct 21, 2007 at 11:07:13PM +0100, Paul Cager wrote:
> What about if we follow this algorithm to determine JAVA_HOME (assuming
> it is not already set)?
>
> (1) Keep following the symbolic link /usr/bin/java until you get to
> a plain file.
>
> (2) Traverse up the direc
Michael Koch wrote:
> On Tue, Oct 02, 2007 at 06:37:55PM +0200, Krzysztof Sobolewski wrote:
>> 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.
>
On Tue, Oct 02, 2007 at 06:37:55PM +0200, Krzysztof Sobolewski wrote:
> 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
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
5 matches
Mail list logo