What do we think about this as a best
practice for managing dependencies?
Keep all dependencies specified in the top
level pom's dependencyManagement section.
Specify scope and version in child projects,
only when scope and version need to be
those provided in the top level pom.
The mojo that analyzes a build's pom structure would
then traverse all the poms looking for exceptions to
this and would generate a report containing
recommendations for conforming to this rule.
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.