https://blog.devops-monk.com/tags/modules/Recent content in Modules on Devops MonkHugoen-usSun, 10 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java25/module-import-declarations/Sun, 10 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java25/module-import-declarations/The Problem: Import Hell Every Java developer has experienced this. You open a file and before you see a single line of business logic, you wade through a wall of imports: import java.util.ArrayList; import java.util.Collections; import java.util.HashMap; import java.util.HashSet; import java.util.List; import java.util.Map; import java.util.Optional; import java.util.Set; import java.util.function.Function; import java.util.function.Predicate; import java.util.function.Supplier; import java.util.stream.Collectors; import java.util.stream.Stream; import java.io.BufferedReader; import java.io.FileReader; import java.io.IOException; import java.nio.file.Files; import java.nio.file.Path; import java.nio.file.Paths; import java.https://blog.devops-monk.com/tutorials/java11/module-system/Mon, 04 May 2026 00:00:00 +0000https://blog.devops-monk.com/tutorials/java11/module-system/The Problem JPMS Solves Before Java 9, the JDK had no real notion of encapsulation at the library level. public meant accessible to everyone — including internal JDK classes like sun.misc.Unsafe and com.sun.internal.*. Large codebases suffered from: No reliable encapsulation: Any public class in any JAR was reachable from any other JAR. Classpath hell: Duplicate or conflicting classes from different JARs led to unpredictable behaviour. Monolithic JDK: The entire 60+ module JDK had to ship with every application.