Then you can only build your project from the top level. Maven *will not* go into mod1 and build it automatically when you are building in mod3. But it will build each of your modules in order if you have a parent pom in that top level (what you are calling project) and specify mod1, mod2, and mod3 as modules.
Maven has certain requirements to function properly; primary among them is the usage of a local repository where artifacts are installed, so they can be properly found and re-used later, etc. So you *must* install the artifacts if you aren't going to build from the top level every single time. Wayne On 6/1/06, Eugeny N Dzhurinsky <[EMAIL PROTECTED]> wrote:
I have some project which consists of several modules. Some of modules depends of another modules. project |-module1 |-module2 |-module3 I would like to be able to build single module and all modules it depens on if required. If I change directory to 'module3' and try mvn compile, maven complains it can't find dependency 'module1' because I didn't installed it (with mvn install). I don't want to install module1 into repository. -- Eugene N Dzhurinsky --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
