What are the advantages of sticking to the default maven project directory structure?
Simply put, if you are using maven, should you treat maven layout as the gold standard, or should you convert your layout to suit your tools (WASD, myEclipse, RAD, etc.)?
Realizing that maven is customizable and you can override the defaults in the Super POM, I am trying to determine if I should change the layout to support certain tools that are in the house, or try to get those tools to recognize the maven layout.One thing to follow Consider is the possible integration of continuous build tools as well as various IDEs in the game. Currently using MyEclipse, but that means they won't renew licenses after 6 months.
The first question I asked about this kind of thing was too specific and one-sided.
a source to share
Maven follows the "Convention over Configuration" principle, which means that if you follow your conventions, you don't need to override basic information such as your project structure.
As far as I know, I prefer to have the shortest pom.xml I can write and I don't like defining information like where to look for sources, resources, etc.
In addition to this, having the same structure for multiple projects is an obvious benefit, especially if you have many management applications. It also helps new developers understand the app if it follows some conventions ...
a source to share
Like all "best practices", take it for what it's worth. As you note, IDEs can have a specific project structure that they like - since most of your development is actually done in the IDE, that's how developers will actually think about problems.
If you standardize your store around a standard project structure, you can always define this general structure in a common company POM file.
a source to share