I run into the same problems...
running mvn install, puts module 'A' in your local repository where it can
be found when doing a compile for module 'B'
-but-
if im doing development on both modules.. I dont want the old version of
module 'A' to be used when im compiling module 'B' - I want it to pick up my
latest changes.
I suspect we are missing something in the way maven was designed to work.
How is multi-module development intended to work?
On Fri, Oct 1, 2010 at 4:38 PM, David Jencks <david_jencks@yahoo.com> wrote:
> Have you run mvn install?
>
> david jencks
>
> On Oct 1, 2010, at 4:12 PM, Iron Eagle wrote:
>
> > Hi there,
> >
> > I have a multi module project with a parent, module A and module B. I
> configured each module pom with the parent and added the modules to the
> parent pom.
> >
> > Module B depends on module A, so I added the dependency in module B. When
> I now package or compile the entire project within the parent directory,
> first module A is created and then module B is creates successfully with
> module A.
> >
> > But when I try to compile module B within the directory of module B,
> maven tells me, that the dependency to module A can not be resolved. Can
> this behaviour changed, so that it is possible to compile module B within
> its directory successfully?
> > --
> > GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit
> > gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>