Bug 1508822

Summary: java-9-openjdk-headless pulls in java-1.8.0-openjdk-headless
Product: [Fedora] Fedora Reporter: Marko Myllynen <myllynen>
Component: java-9-openjdkAssignee: jiri vanek <jvanek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: dbhole, jerboaa, jvanek, mvala, omajid, sgehwolf
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-02 10:25:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marko Myllynen 2017-11-02 10:03:13 UTC
Description of problem:
java-9-openjdk-headless requires javapackages-tools which in turn pulls java-1.8.0-openjdk-headless which obviously is unwanted.

Perhaps this is more a javapackages-tools issue and should be reassigned but filing initially against java-9-openjdk to raise awareness. Thanks.

Version-Release number of selected component (if applicable):
javapackages-tools-5.0.0-7.fc27.noarch
java-9-openjdk-headless-9.0.0.181-7.fc27.x86_64

Comment 1 Severin Gehwolf 2017-11-02 10:25:45 UTC
Thanks. We are aware. This is a duplicate of bug 1500288.

*** This bug has been marked as a duplicate of bug 1500288 ***

Comment 2 Marko Myllynen 2017-11-02 13:15:25 UTC
FWIW, I'll note here for the record that before bug 1500288 is fixed, after installing java-9-openjdk on Fedora 27, the default java alternative gets set to java-1.8.0-openjdk.

Comment 3 jiri vanek 2017-11-02 13:27:28 UTC
(In reply to Marko Myllynen from comment #2)
> FWIW, I'll note here for the record that before bug 1500288 is fixed, after
> installing java-9-openjdk on Fedora 27, the default java alternative gets
> set to java-1.8.0-openjdk.

Another note: This behaviour will persist  fixing of this bug. Jdk9 is to fragile   to have higher priority then jdk8