3 ms·
> All that work, which broke plenty of Java applications, violating main Java mantra of backward compatibility, all for nothing. How did modules break Java app
by pgwhalen 5y ago
> All that work, which broke plenty of Java applications, violating main Java mantra of backward compatibility, all for nothing.
How did modules break Java applications? Having recently upgraded a number of applications from 8 to 11, none of the things we had to fix were due to modules. They were largely due to libraries relying on internal implementation details of Java 8 which needed dealing with, the exact sort of thing that modules are looking to prevent going forwards (see "strong encapsulation" in TFA).
We've ignored modules so far with no issues.
- krzyk 5y agoHe probably writes about removal of some EE classes that were in JDK (but shouldn't). Or better protection of Java internals (warnings about using internal classes in JDK 11, and in JDK 17 no warnings - you need to --add-opens or don't use broken lib).
- pgwhalen 5y agoYeah, the removal of EE classes was probably the biggest burden for my team (completely unrelated to modules).