> 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????
This isn't really a Maven question. Instead you're asking about general Software Engineering and Architecture, and you happen to be using Maven as your build tool. If you were using Ant or make, would your questions be any different? I'm not aware of any guidelines published by Maven that will help you decide when to make something a submodule of a project vs its own top-level project. It is an interesting topic so maybe this thread will prove useful to you and some practical conventions will shake out if this turns into a real discussion topic. I'd just keep things as modules and keep versions all locked together until it no longer makes sense to do so, then split specific modules off into their own top level project. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
