9287 – Blackdown JDK does not register itself

Bug 9287 - Blackdown JDK does not register itself

Summary: Blackdown JDK does not register itself

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Unspecified (show other bugs)
Hardware:	x86 Linux

Importance:	Lowest normal (vote)
Assignee:	Java team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-10-18 04:49 UTC by Jacob Atzen
Modified:	2003-02-04 19:42 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jacob Atzen 2002-10-18 04:49:44 UTC

According to the java documentation on the gentoo.org website, the blackdown-jdk
should be listed when running 'java-config --list-available-vms'. This is not
the case. 

Apparently the ebuild does not place anything in /etc/env.d/java as I believe it
is supposed to (not too sure about that though).

As a consequence of this it is not possible to set the system-vm or user-vm to
blackdown-jdk with the java-config tool. Furthermore this makes it impossible to
install openoffice from source, as it requires the blackdown-jdk.

Comment 1 Karl Trygve Kalleberg (RETIRED) gentoo-dev

2002-10-18 16:11:02 UTC

This is a bug in Portage; if you merge the jdk more than once, the files will be
removed. 

Carpaski, any progress on this one ?

Comment 2 Adrian Almenar 2002-12-09 17:32:36 UTC

This is fixed in the updated java.eclass