Some ebuilds depend on virtual/jre and that will install blackdown-jre even if a JDK is installed. Sun's JDK and Blackdown's JDK also offer a runtime environment so it is unnecessery to merge blackdown-jre when a JDK is already installed. virtual/jdk should also provide virtual/jre
I just noticed that the virtual file has changed: virtual/jre dev-java/blackdown-jdk The bug reported is fixed but anyway: that's a not-so-nice solution because if you have a jre installed and it would be enough to run the app the jdk gets merged nevertheless... the only "real" solution would be to make one virtual providing another like the summary of this bug says...but unfortunatly that doesn't work ATM
bug finally closed by changing the virtuals file (was already changed weeks ago, this solutions seems to be the one everybody accepts. Also, the bug originally reported ["virtual/jre will install blackdown-jre even if a JDK is installed"] is fixed) virtual/jdk dev-java/blackdown-jdk virtual/jre dev-java/blackdown-jdk