Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
Don't Know (Unsure) - The default level
Description
This is something me and Michael Starch debated at apachecon and I've been wanting to do for a long time.
Most multi module projects I work with have their dependency versions set at the top level that way its easy to change the dependency version for the project and keep everything in sync across the whole build rather than (as in one case I found) have 4 different versions of the same dependency.
I've moved them all to the core pom and ordered them alphabetically, if no one is too unhappy with this I'll finish off the reordering in the other poms and we can continue as usual. I've tried a local build nothing fails(although who knows once it hits jenkins), and if there really is a need to override a specific dependency version on a per module basis this can still be done.
Personally I think its a useful tidy up and of benefit to the developers new and old.