It is hard to understand your example.
Can you define "child" and "grandchild" and clarify where the
dependencies are coming from (Third parties? Other children?)
In general, you use the parent to define properties and define the exact
versions of dependencies in a dependency management section.
Children define the dependencies that they require but not the versions.
What is the choice that you are trying to make that you think needs to
follow a "best practice"?
You might want to mention what kind of application you are building
(language, type of app, target platform).
Ron
On 21/08/2015 5:37 AM, aalok singhvi wrote:
Hello,
Any best practices on how to arrange dependency in multi module maven
project.
Let me give an example
Parent Project
Child1
GrandChild1 ( Depedency1, Dependency2, Dependency3)
GrandChild2 ( Depedency1, Dependency2, Dependency, 4)
GrandChild3 (Depedency1, Dependency2, Dependency, 5)
GrandChild4
(Depedency1, Dependency2, Dependency3, Dependency4, Dependency,
5)
Child2
GrandChild1 ( Depedency1, Dependency2, Dependency3)
GrandChild2 ( Depedency1, Dependency2, Dependency, 4)
GrandChild3 (Depedency1, Dependency2, Dependency, 5)
GrandChild4
(Depedency1, Dependency2, Dependency3, Dependency4, Dependency,
5)
How can you set dependency properly so that it will available to
GrandChild4 as well.
Looking forward to your reply.
Thanks
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
