What version of Maven are you using? Have you tried 3.0.1? Out of a module design perspective, I find your structure strange and I think that you should try to re-arrange. In some sense you do have cyclic dependencies, as utils depends on mid, while mid depends on utils.
/Anders On Tue, Jan 4, 2011 at 03:19, Hayarobi Park <[email protected]> wrote: > Hello, > > I'm managing maven project of my team, and having truble in module > dependencies.. > > The root project has some sub modules. > A submodule named "utils" has a few submodule; config, logger, json and > etc. > Another submodule "mid" has "manager" submodule, which are pom project and > has core, clientAPI and protocol sub modules. > > The problem is that utils:config depends on mid:manager:clientAPI, > mid:manager:clientAPI depends on utils:logger and utils:json, and the other > modules in mid:manager depend on submodules utils, including config. There > are not cyclic, but twisted dependencies, and maven can't solve the > dependency well. > > I have to do tedius steps to build whole project in the new configuration. > 1. install utils first, maven complains and stop building utils:config > since mid:manager:clientAPI was not installed yet, just after installing > utils pom project. > 2. go to utils:logger and install, and for utils:json respectively. > 3. go to mid directory and install mid, maven will install mid and stop > further install caused by dependeny on utils:config of some other submodules > of mid. > 4. go to mid:manager and install it. > 5. go to mid:manager:clientAPI and install it. > 6. go to utils:config and install it. > 7. Finally, go to top level and install whole modules. > > How to solve this situation? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
