I'm new to maven and very much used to the "application per eclipse project, and common library per eclipse project".
I know "multi module vs. flat" has been discussed multiple times on this list, but I've not seen general "pros/cons, rules of thumb, etc." of when an application should be part of a multi-module vs. split out to another eclipse project. I'm going under the assumption in the "maven way" it's OK to have multiple applications living as part of a multi-module, for example foo_webapp and cmd_line_client both dependant on lib_a MyMultiModuleProject ->lib_a ->foo_webapp ->cmd_line_client But what decides that foo_webapp and cmd_line belong here, just their dependency on lib_a and the desire to share pom config & version them together? For example, should a few new applications, also dependent on lib_a should live here? When does it end? Or perhaps if "lib_a" is expected to be widely reusable it should live outside the multi-module...or???? Any links to references greatly appreciated... Thanks for your input! Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
