I\'ve done a bunch of Java coding recently and have got used to very specific package naming systems, with deep nesting e.g. com.company.project.db
. This works fine
Java packages are not nested, they're flat. Any apparent nesting is nothing more than a naming convention.
For example, the package com.company.project.db
has no relation whatsoever to com.company.project
or com.company.project.db.x
. Code in com.company.project.db
has no more access to code in com.company.project.db.x
than would code in a.b.c
.