Hi, you're saying:
> 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 ). > This would be an even bigger problem during install/deploy calls: What would then happen if changed some parts in subproject A and B and try to use parts of A in B? Since A will not be deployed/installed prior to the compilation of B, you might download the wrong version of A from the repository. This would lead to broken builds!? Currently it is like that: subproject A - compile subproject A - test subproject A - jar subproject B - compile <- in need of a subproject A jar (searching in repostitory) subproject B - test <- proceeds only if an OLDER version is found subproject B - jar subproject A - install subproject A - deploy subproject B - install subproject B - deploy Should a project not go through the whole build lifecycle first before switching to the next project??? M -- View this message in context: http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8277154 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
