This question already has an answer here:
- Is a common library a good idea? 5 answers
I am trying to develop my package structure based on features rather than layers, but am struggling to find a package name for some of the classes. I have seen people use a package name of
common for classes that seem to span multiple packages, but I cant seem to find any good resources on the best way to go about deciding what should be in a common package. Do classes in common need to be used by multiple other packages/modules to be considered "common"? Is this just a package for putting classes that don't fit in anywhere else?
Any advice is greatly appreciated.