root
> pom.xml everything works well, but if I just want to work with a
> sub-module, than extra steps are required.
>
> -Chris
>
> -Original Message-
> From: Gareth Western [mailto:[EMAIL PROTECTED]
> Sent: March 28, 2006 2:50 PM
> To: Maven Users List
> Subjec
ct: Re: RE : [m2] Inter-project dependency question
Hi Chris,
I'm not sure if this is the BEST way to do it, but what I do is create a
parent pom.xml in the root directory. Then add commons, web-app, and
stand-alone app as modules in that parent POM. Maven should figure out
that
since webapp
Hi Chris,
I'm not sure if this is the BEST way to do it, but what I do is create a
parent pom.xml in the root directory. Then add commons, web-app, and
stand-alone app as modules in that parent POM. Maven should figure out that
since webapp and standalone app are dependent on the commons module th
-Original Message-
From: Olivier Lamy [mailto:[EMAIL PROTECTED]
Sent: March 28, 2006 12:01 PM
To: 'Maven Users List'
Subject: RE : [m2] Inter-project dependency question
Perso I do as this.
root
-- commons 1.0-SNAPSHOT
-- webapp
-- sub module A (depends on commons 1.0-SNAPSHOT)
is compatible).
When commons is released, changed the version dependency in others
modules.
And just work in sub module A.
- Olivier
-Message d'origine-
De : Chris Wall [mailto:[EMAIL PROTECTED]
Envoyé : mardi 28 mars 2006 19:53
À : Maven Users List
Objet : [m2] Inter-project depen
This is probably a fundamental question for most of you...
Considering the following project structure...
root
-- commons
-- webapp
-- sub module A
-- sub module B
-- stand-alone app
... since the webapp project has a dependency on commons (as does the
stand-alone app), how do I te
