Hello again, We were discussing this on the Apache directory dev list as well, and Greg Duffy provided some clarification.
So I attempted to come up with a best practice around it. If you have a chance it would be great to hear more feedback on this. Here is my answer to Greg. OK - I think the lights are starting to turn on now. If we put them in dependency management, they are not automatically included, whereas if we put them in dependencies, they are automatically included for all children. So if I were to write a best practice... I could say that only dependency management should be used in the parent, and dependencies should be explicitly listed on each kid. That way some of the kids don't end up with dependencies they don't really need, and we have the benefit of being able to update the version in one place. I'm leaning toward this as a best practice, because we could have a build that has 3 modules and then we add a 4th one, and if the parent had dependencies included in the pom, the 4th module automatically gets them, and maybe it didn't really want them. Thoughts? Thanks Greg, - Ole --- Ole Ersoy <[EMAIL PROTECTED]> wrote: > Hi, > > I'm working on a mojo that will analyze a build's > poms and come up with structuring recommendations. > > For dependencies I had a simple rule in mind. > > Keep them either on the parent or the child, unless > one of the children has to override the parent's > version setting...so this would only happen if a > parent had 3 children, two of which needed the same > version and a 3rd > needing a different version. > > However Maven also has the dependencyManagement > element. > Does that do something that the regular dependencies > element does not? > > Also, if anyone has other pom structuring rules / > best > practices they would like to see included in the > report > I'm accepting requests. The report mojo will be > apache licensed. > > Cheers, > - Ole > > > > > > ____________________________________________________________________________________ > Do you Yahoo!? > Everyone is raving about the all-new Yahoo! Mail > beta. > http://new.mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ____________________________________________________________________________________ Have a burning question? Go to www.Answers.yahoo.com and get answers from real people who know. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
