Places to run "mvn compile": /projects/torsten/ -- success with nothing installed /projects/torsten/submoduleA, no dependencies -- success with nothing installed /projects/torsten/submoduleB, depends on A -- A must be installed for compile to be successful /projects/torsten/submoduleC, depends on B -- B must be installed for compile to be successful
As a result, I generally run "mvn compile" from the parent directory, so I don't have to worry about what's installed and what isn't. Wayne On 1/17/07, Dan Tran <[EMAIL PROTECTED]> wrote:
When you are INSIDE a module/project, the only way that maven can locate the dependencies is via local repository. An therefor all your dependent module must be installed.. However if you use the parent to build all modules, you dont have to run "maven install" but "maven compile" would do since maven is aware of all module's classes directory -Dan On 1/17/07, Dipl.-Ing. Torsten Liermann <[EMAIL PROTECTED]> wrote: > > (Sorry, I can not speak english). > > My question: > > Must I install modules before compiling an other module with dependcies > to modules? Or is there a way without installing modules and start > compilation > within modules directory? The compilation from the parent directory > works fine... > > Thanks, > Torsten > > --------------------------------------------------------------------- > 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]
