Hello everybody,
I'm working on a quite big project using a maven multimodule project layout. I
learned quite a lot about Maven the last month and I'm happy to use this tool.
Currently, I'm wondering about a issue, I couldn't find a guide or a hint for
best practice for.
I'm using a dependency management section at the root pom for managing project
external dependencies like mysql connector, or spring framework version.
It is perfectly clear to me, to use dependency management here.
But what about project-internal dependencies? Should I also include each leaf
of my project tree (i.e. each module with packaging type jar) in the dependency
management section, with the project.version as its version?
Like this?
<dependency>
<groupId>ourGroup</groupId>
<artifactId>rootmodule.submodule1.subsubmodule1</artifactId>
<version>${project.version}</version>
</dependency>
What is the best practice here?
Furthermore, if I run a compile on the root pom, I get the feeling, that maven
does not try to find project-internal dependencies by traversing the
multi-module-project, but looking up the local repository. Can this behaviour
be changed? Otherwise, I always have to redeploy the modules, other modules
depend on, to the local repository before I can compile the module itself...
I hope you get the problem!
Nonetheless, thanks a lot for this great tool, that really helps me developing
and following good development practice!
Regards,
Flo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
