Good day to you, Trevor, Let me get this straight, you have a subproject that depends on the other subprojects? If so, then you don't have to worry about which projects would be installed first in your local repository. When you execute a maven command on a project with modules (subprojects), it will automatically traverse through the subprojects ( and their subprojects, etc ) and arrange them in order of dependencies. This is to make sure that if A depends on B, B will be built first.
If a dependency of your maven project does not exist when you execute a maven command, then that project will not bulid ( assuming ofcourse the maven command requires a pom to execute ). So if you want, you create first your dependencies, then their dependees. Cheers, Franz Trevor Torrez wrote: > > Is it the suggested / best practice to have a subproject in a multi > project > setup to declare it's dependencies on the other subprojects in the > dependency section? This leads to requiring some parts of the > multi-project > to be installed to the local repository before other parts can be > developed > (using the eclipse:eclipse goal fails if the dependency / subproject is > not > installed). Or is there a better way? > > -- View this message in context: http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8154936 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
