nd therefore module A will not be in the reactor. This
> is
> > > why the m2 repo will always be used for module A in this scenario.
> > >
> > > Joe
> > >
> > > -Original Message-
> > > From: Siddharth Jain
> > > Sent: Thur
m2 repo will always be used for module A in this scenario.
> >
> > Joe
> >
> > -Original Message-
> > From: Siddharth Jain
> > Sent: Thursday, February 15, 2024 7:50 PM
> > To: Maven Users List
> > Subject: Re: How does maven resolve
> module build - and therefore module A will not be in the reactor. This is
> why the m2 repo will always be used for module A in this scenario.
>
> Joe
>
> -Original Message-
> From: Siddharth Jain
> Sent: Thursday, February 15, 2024 7:50 PM
> To: Maven User
A will not be in the reactor. This is why
the m2 repo will always be used for module A in this scenario.
Joe
-Original Message-
From: Siddharth Jain
Sent: Thursday, February 15, 2024 7:50 PM
To: Maven Users List
Subject: Re: How does maven resolve inter-module dependencies in a multi-module
build
thanks Joe. but then if classes are available both in the target directory
of module A as well as a jar file in M2 repository which takes precedence?
also i have noticed that while running mvn compile from the root works,
running mvn compile from the directory of B does not pick up classes from
Hi Sid,
It will resolve the classes directory of module A that will have been populated
during module A's 'compile' build.
Joe
On 2024/02/15 17:50:44 Siddharth Jain wrote:
> Hello,
>
> I am working on a multi-module Maven build. e.g., I have a root directory
> containing 3 sub-projects A, B, C
Hello,
I am working on a multi-module Maven build. e.g., I have a root directory
containing 3 sub-projects A, B, C and a parent pom defined in the root
directory. I notice that I can run mvn compile from the root directory and
it will build the 3 projects. The projects may have inter-dependencies
