Many times, I am trying to resolve several basic or complex Maven / Java EE project structure issues, on my day work. In order to provide the solutions, I often end up experimenting with the project structure and it’s effectiveness.
It’s worth investing some time on application structure for big projects (especially Java EE). If not, it’s cannot be changed at the end.
It’s important to understand the application structure and the underlying build tools when you start working on a project.
Maven might be wise choice because it’s helps you build a better project quickly and effectively.
Maven helps in the following areas :
- Making the build process easy
- Providing a uniform build system
- Providing quality project information
- Providing guidelines for best practices development
- Allowing transparent migration to new features
Best practices (maven’s) for development
- Keeping your test source code in a separate, but parallel source tree
View original post 449 mots de plus