Question: Are development tools planned?

[e-reznik]

Hello,

I was wondering whether the book plans to cover popular development tools, like:

• Git
• Maven or Gradle
• JUnit (or testing in general)

Currently, the book focuses on core language features. However, for many learners, understanding how Java projects are structured and built in practice is an important next step.
Is tooling intentionally out of scope, or is there a plan to include a section on real-world Java development workflow?

Thanks!

[bowbahdoe]

It's not out of scope. What I struggle with though is how to iteratively build up to that point.

For instance look at where it ends right now - I explained modules and multi module projects and also how to put things into jars. That is the natural way the language would frame a library.

But those multi-module project layouts supported by the compiler and the way libraries are distributed in the maven world are at odds.

I can certainly build up and say "yeah ignore what I said so far" or contextualize things differently or make my own tool that slots in the middle, but it's tough.

Essentially I'm a prisoner of my own desire to not jump the shark. The ecosystem right now demands a shark jumping.

The best I can do right now is just inch my way forward and hope I eventually reach enough background knowledge that I can explain those things. That or the jdk includes a mechanism for dependency resolution itself.