Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLOUD-3044 move jdk8 removal from jdk11 module to maven module #322

Merged
merged 1 commit into from Jan 29, 2019

Conversation

rcernich
Copy link
Contributor

@rcernich rcernich commented Dec 6, 2018

Signed-off-by: rcernich rcernich@redhat.com

Thanks for submitting your Pull Request!

Please make sure your PR meets following requirements:

  • Pull Request title is properly formatted: [CLOUD-XYA] Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains description of the issue
  • Pull request does not include fixes for other issues than the main ticket
  • Attached commits represent unit of work and are properly formatted
  • You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
  • Every commit contains Signed-off-by: Your Name <yourname@redhat.com> - use git commit -s

http://issues.jboss.org/browse/CLOUD-3044

@rcernich rcernich changed the title move jdk8 removal from jdk11 module to maven module CLOUD-3044 move jdk8 removal from jdk11 module to maven module Dec 6, 2018
Signed-off-by: rcernich <rcernich@redhat.com>
@rcernich
Copy link
Contributor Author

rcernich commented Dec 6, 2018

@jmtd, fyi

@@ -13,20 +13,12 @@ pushd ${ARTIFACTS_DIR}
cp -pr * /
popd

# As of rhel 7.6, rh-maven35 pulls in jdk8, so we need to remove them
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a bug in the maven SCL package. Has it been reported in Bugzilla?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but it won't be fixed. The dependency for rh-maven35 is on java-devel and jdk 11 provides java-11-devel, so rh-maven35 doesn't see the jdk 11 install and install jdk 8 over top of it. The alternatives --set will ensure that jdk 11 is the default, as it will be installed first (maven module depends on jdk module), even if jdk 8 is installed. The maven module checks to see if jdk 11 is the default and, if it is, removes jdk 8. Note, this whole configuration prevents the installation of multiple jdks (because the jdk modules have the same id).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but it won't be fixed. The dependency for rh-maven35 is on java-devel and jdk 11 provides java-11-devel,

I think jdk 11 should be providing both java-devel and java-11-devel.

Copy link
Collaborator

@jmtd jmtd Dec 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think jdk 11 should be providing both java-devel and java-11-devel.

Sorry for the terseness of my message. To expand: I'm interested in pursuing fixing this in the right place (rpm permissions)) with my new team hat on (or at least learning why it will never be fixed). But in the mean time, working around it in the module as with this PR is the right thing to do (as we did for the JDK7→8 transition period, when the same thing happened). So I will review this PR properly ASAP

Copy link
Collaborator

@jmtd jmtd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants