[
https://issues.apache.org/jira/browse/OODT-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesha Sudasingha updated OODT-863:
-----------------------------------
Fix Version/s: (was: 2.0)
(was: 1.9)
> Tidy up dependencies
> --------------------
>
> Key: OODT-863
> URL: https://issues.apache.org/jira/browse/OODT-863
> Project: OODT
> Issue Type: Sub-task
> Reporter: Tom Barber
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
