java - Project structure organization: how to make it better? -
All -
There are many web applications, based on some versions of the spring developed all the time But different teams in the organizations they each make their war, put a different context to work within, and often get deployed on the same machine, because their functionality is knit together. So we end up with:
On deployment, each one is very Use the same set of tool chains, repeat all around the spring jar and dependence. I am thinking that there is a way to improve project structure, single each webpage resides in its own source repo and speeds up its own growth? ? Any pointer or reference much appreciates. Oliver You probably have to take an app server like jboss , But can not you use the ear file and you can create Maven for the module? In this way you can put them in different repos, if you want to do it with your pom and then there is another project with a palm for the ear file: Here the Maven Cannes plugin Is: < / html> tomcat / webapps / {A, B, C ...}
Comments
Post a Comment