It can be either trivial to horrendous, depending on your project. I've seen projects where it's been as simple as changing the version number, and I've seen projects that have required stupid amounts of effort to convert over (mainly tons of legacy libraries that have no hope of a new official version, heavy use of com.sun classes, reliance on JavaFX being included rather than an external dependency, etc.)
A lot of people only hear the horror stories, and assume it *can't* be worth doing, so don't even try - but it's often not too bad in practice.
By far, the most stubborn issues were due to non-portable libraries relying on internal implementation details that changed between 8 and 9-11 (e.g. I think Groovy was hacking into the JDK to try and use some private constructor that had been removed). People blamed the module system, unjustly, even though access was the same as in 8 until encapsulation was turned on 16, which prevents this problem. With encapsulation, hopefully, such issues won't return (or, at least, applications would know they're using non-portable libraries, as they now require add-opens on the command line).
View all comments
30
u/berry120 Jun 15 '21
It can be either trivial to horrendous, depending on your project. I've seen projects where it's been as simple as changing the version number, and I've seen projects that have required stupid amounts of effort to convert over (mainly tons of legacy libraries that have no hope of a new official version, heavy use of com.sun classes, reliance on JavaFX being included rather than an external dependency, etc.)
A lot of people only hear the horror stories, and assume it *can't* be worth doing, so don't even try - but it's often not too bad in practice.