Why are project layout resources kept separate from Java sources?

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 source files which, when "compiled", just need to be copied as-is with the classes, and eventually packaged in the jar, and accessed by the *classloader*'s methods `getResource`/`getResourceAsStream`, via the `classpath`. Personally I find it a useless complexity to keep resource files separate from Java sources. 1. What do you think? 2. Is there a good reason why maven keeps resources separate from sources? 3. Is there any counter indication in not using `src/main/resources` and `src/test/resources` and keeping resources in `src/main/java` and `src/test/java` using maven?

以上就是Why are project layout resources kept separate from Java sources?的详细内容,更多请关注web前端其它相关文章!

赞(0) 打赏
未经允许不得转载:web前端首页 » JavaScript 答疑

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址

前端开发相关广告投放 更专业 更精准

联系我们

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

微信扫一扫打赏