Summary

Conclusions

JPMS defines access boundaries, the build file defines reproducible tools and dependencies, and JUnit defines verifiable contracts. Together they let you evolve a program without depending on the incidental settings of a single IDE, and they prepare the ground for JDBC and JavaFX projects.

Self-check questions

1. How do exports and opens differ?
2. When does an API client need requires transitive?
3. Why is Maven install not an application installer?
4. What does the Wrapper pin, and what does it not pin?
5. Why do zero tests found not mean success?
6. Which bug will even 100 % line coverage not detect?