How to organize larger Java projects - Projects vs. Namespacing?
<p>I'm wondering if there is some recommended reading, best practice or opinion on how to organize larger Java projects. </p>

<p>I made the observations that there are folks who split up everything into projects (i.e. modules) and create many many projects that share a web of dependencies. This has the advantage that compilation is often super fast, but when the project gets large nobody knows anymore what depends on what and why. Not talking about dependent libraries, version conflicts &amp; co.</p>

<p>The alternative is to have just a couple of projects such as frontend, backend, ... . The namespacing does the job. </p>

<p>Any opinion, further reading anyone could recommend?</p>
