I understand, I did the same mistake at first. A good way to understand a
maven parent pom project, is to look at it like it was a workspace in a IDE.
The projects still have to declare the dependencies over their sibling
projects.
On 11/3/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
>
> thank you.
thank you. i guess i misunderstood the way maven works. i initially
thought that the reactor (or whatever internal component) also keeps
track of the compiled classes.
ciao!
On 11/3/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> You have to declare module1 as dependency in module2. Maven cann
You have to declare module1 as dependency in module2. Maven cannot guess it
automatically. Add this in your Module2 pom.
root.MODULES
module1
1.0
Voilà, it should work now. Hope this help!
On 11/3/05, Anuerin Diaz <[EMAIL PROTECTED]> wrote:
>
> hi,
>
> i am starting a multi-module project t
hi,
i am starting a multi-module project that has this structure
root
|---module1
|-pom.xml
|---module2
|-pom.xml
|-pom.xml
wherein module2 depends on module1. compilation of module1 goes
fine but module2 fails because it cannot see the classes in module1. i
hope
