Perso I do as this.

root
  -- commons 1.0-SNAPSHOT
  -- webapp
    -- sub module A (depends on commons 1.0-SNAPSHOT)
    -- sub module B (depends on commons 1.0-SNAPSHOT)
  -- stand-alone app (depends on commons 1.0-SNAPSHOT)

In the root directory, mvn clean test-compile. (in order to verify all
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 dependency question


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 tell M2 to build commons, if it's not
already, from within the webapp module (webapp/pom.xml)?
 
Thanks.

-Chris

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



This e-mail, any attachments and the information contained therein ("this 
message") are confidential and intended solely for the use of the addressee(s). 
If you have received this message in error please send it back to the sender 
and delete it. Unauthorized publication, use, dissemination or disclosure of 
this message, either in whole or in part is strictly prohibited.
--------------------------------------------------------------------------------------------------------------
Ce message électronique et tous les fichiers joints ainsi que  les informations 
contenues dans ce message ( ci après "le message" ), sont confidentiels et 
destinés exclusivement à l'usage de la  personne à laquelle ils sont adressés. 
Si vous avez reçu ce message par erreur, merci  de le renvoyer à son émetteur 
et de le détruire. Toutes diffusion, publication, totale ou partielle ou 
divulgation sous quelque forme que se soit non expressément autorisées de ce 
message, sont interdites.
-------------------------------------------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to