This is not really a maven. You might want to ask in the Java community.
My advice would be to group the code into projects in such a way that changes affect the smallest number of projects. On the other hand, you also want to make it easy to figure out which project contains the class that you want to change.
Ron On 26/04/2013 11:03 PM, zhu19774279 wrote:
For example, I have a SSH project, how many modules should I split? A service-module, a DAO-module, a action-module and a web-app module? Are there any guidelines or rules I should follow? Thanks~~ -- View this message in context: http://maven.40175.n5.nabble.com/Are-there-any-guidelines-I-can-follow-when-I-split-apart-a-wep-app-into-a-multimodule-project-tp5754421.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- Ron Wheeler President Artifact Software Inc email: [email protected] skype: ronaldmwheeler phone: 866-970-2435, ext 102 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
