-
Notifications
You must be signed in to change notification settings - Fork 495
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
Spike: Java 9 and Java EE 8 #4217
Comments
I don't believe it makes sense to upgrade to Java 9 at this time. It's only been out for a few weeks so Linux vendors haven't had time to package it as The next question is, "When will we be able to simply run |
Today at our architecture meeting we talked a bit about Glassfish 5 vs Payara. I believe the primary thing our customers want is security. At @bjonnh said, "I'm annoyed that we have to use horribly old software and be stuck with it." @donsizemore opened #4172 asking about Payara support. The thing about Payara is that it's updated more regularly than Glassfish. Here's a little chart I made from a spreadsheet I made based on release dates on Wikipedia. Note how regular the Payara releases are: More regular releases probably means better security, right? I would hope so. Anyway, over at #4172 I'm asking when we should expect Payara 5 because it would be nice to upgrade to the latest major version if we can. As @landreev mentioned in the meeting today, maybe it wouldn't be too tough to support both Glassfish and Payara. I'm not sure. So far I've been hacking a bit on trying to get Dataverse running on Glassfish 5 and I assume that work will carry over fine to Payara 5. I'll push a branch once I have something to show. At a high level, we need to update the following:
We might need to change our Java code itself but I hope not. We'll see. |
I missed sprint planning yesterday but I heard this issue got moved to the backlog. At standup I mentioned I'd push what I was working on to my fork, which I just did: pdurbin@d757099 |
I just made pull request #4244 for upgrading to Glassfish 5. I'd like to get some Code Review on it so I'll move it to that column at https://waffle.io/IQSS/dataverse As I indicated above, it's premature to upgrade to Java 9. I also did not bump the Java EE version from 7 to 8 in pom.xml. Let's do this in small chunks. Along the way I also fixed #3905 and probably #2443. Basically, I started using the official installer for the first time on a dev environment. Previously I always used some variation of https://github.com/IQSS/dataverse/blob/v4.8.1/scripts/deploy/phoenix.dataverse.org/install which is much smaller and simpler (and Bash instead of Perl). My main objection to the installer originally is that it required root (that's a lot what #2443 is about) but this is no longer the case. |
Java 9: Looks pretty good, I seem to have it mostly running after a few hours today, but we probably don't want to upgrade yet. Details:
|
confirmed travisci works with oracle 9
Java EE 8: Unsure, blocked by errors still present in Glassfish 5, also facing a number of issues on its own or ones compounded with Glassfish 5.
This is as far as I went, I need a better understanding of which resources we need to upgrade. I can try to fix these first lines of issues and push forward but its hard for me to tell if issues from Glassfish 5 could also be @ play. |
Thanks @matthew-a-dunlap for creating a well-informed issue for each upgrade. Those are here: |
An investigation about what needs to be done to upgrade our infrastructure to support:
Output of this spike will be well-informed items detailing the upgrade steps and things to test.
The text was updated successfully, but these errors were encountered: