Bug 196238 – azureus,tomcat,limewire are trying to merge jre1.6.0 while sun-jdk1.6.0.02 is already exist

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Thai 2007-10-18 02:45:03 UTC]

lightportal ~ # java-config -L
The following VMs are available for generation-2:
*)      Sun JDK 1.6.0.02 [sun-jdk-1.6]
lightportal ~ # ls /opt/sun-jdk-1.6.0.02/
bin  include  jre  lib  man  src.zip
lightportal ~ # emerge -pv azureus

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] dev-java/javatoolkit-0.2.0-r1  20 kB 
[ebuild  N    ] virtual/jre-1.6.0  0 kB 
[ebuild  N    ] dev-util/desktop-file-utils-0.12  341 kB 
[ebuild  N    ] dev-java/ant-core-1.7.0  USE="-doc -source" 6,683 kB 
[ebuild  N    ] dev-java/bcprov-1.36-r1  USE="-doc -source" 3,047 kB 
[ebuild  N    ] dev-java/commons-lang-2.0-r2  USE="-doc -source" 431 kB 
[ebuild  N    ] dev-java/commons-logging-1.1-r2  USE="-avalon-framework -avalon-
logkit -doc -log4j -servletapi -source" 170 kB 
[ebuild  N    ] dev-java/swt-3.2.2  USE="opengl -cairo -gnome -seamonkey -xulrun
ner" 3,053 kB 
[ebuild  N    ] dev-java/log4j-1.2.14-r1  USE="-doc -javamail -jms -jmx -source"
 2,707 kB 
[ebuild  N    ] dev-java/commons-cli-1.0-r5  USE="-doc -source -test" 37 kB 
[ebuild  N    ] net-p2p/azureus-2.5.0.4-r1  USE="-source" 6,331 kB 

Total: 11 packages (11 new), Size of downloads: 22,815 kB

Reproducible: Always

Steps to Reproduce:
1.emerge virtual/jdk
2.java-config -S sun-jdk-1.6
3.emerge -pv azureus

Actual Results:  
jre 1.6 will be emerged although sun-jdk already includes jre

Expected Results:  
jre will not be merged

tomcat, limewire are trying to merge jre too, not only azureus

[Comment 1 William L. Thomson Jr. (RETIRED) 2007-10-18 03:51:26 UTC]

The emerge output shows only a virtual jre being pulled in. Not a actual jre. If you look at the virtual ebuild you will see

RDEPEND="|| (
                =virtual/jdk-1.6.0*
                =dev-java/sun-jre-bin-1.6.0*
        )"

Which is the main guts of the virtual/jre-1.6.0 ebuild wrt to functionality and what is pulled in by the virtual and etc. So what you are seeing is normal,  and a jre will not be pulled in alongside of the existing jdk. Just the virtual.

Closing as invalid.