Why are project layout resources kept separate from Java sources?

Question

Why does maven keep resources in a separate \"source folder\" from the Java sources?

From my experience, in Java the resource files are mostly treated like Java sou

Answer 1

I think that code/resources separation is often useful:

1. Packages must follow Java specification rules, for example reserved word, like 'int', is not allowed. Having illegal packages in source code folder would be confusing.

2. Resources has instance nature, classes has, well, classes nature. For example you may have classes Continent and Country in the same package but resources better organize as tree:

   • africa/
     • morocco.txt
     • kenya.txt
   • europe/
     • poland.txt

3. Resources structure, in my opinion, is more stable than code structure. Code refactoring happens often, classes move from package to package for better readability. Obligation to move resources on refactoring discourages developer from refactor.

4. If separated resource folder is required even only for 1% of resource files, is reasonable to move remaining 99% to that folder and keep resources in single place only.

However, there are cases when keeping resources and java code together is useful. For example unit tests compares input and output - nice to have file with input and output in the same folder as unit test code.