On Thu, 9 Nov 2017 12:40:00 +0100 Stephen Kitt <[email protected]> wrote: > On Thu, 9 Nov 2017 00:48:47 +0100 > Michael Vorburger <[email protected]> wrote: > > Tomorrow, projects wishing to expose metrics will get use > > dropwizard.metrics by way of an (upcoming) infrautils.metrics > > dependency anyway, instead of a direct dependency to > > dropwizard.metrics in their POM. While we cannot enforce this of > > course, remove it from odlparent dependencyManagement would make it > > clearer IMHO. More importantly though, a quick test reveals that > > parent POM depenencyManagement appears to be "stronger" than an > > indirect transitive dependency - PITA. So, in this specific case, > > best IMHO jst not to have a parent POM depenencyManagement - it's > > not required, and will only cause problems to projects who are > > going to depend on infrautils.metrics. > > ... although in general I’d rather have an actual change in use before > we decide how to migrate. > > I know you’ve heard this already, but it makes it an *awful* lot > easier to get things right if you write something in a project which > uses it, before moving it to somewhere shareable. One day hopefully > you’ll understand this ;-). In this particular case, since having the > dependency management is a hindrance to alternative solutions, and > it’s only used in one project, I don’t mind removing it.
And since the first user of infrautils.metrics would be infrautils.jobcoordinator, my comment on project placement is no longer an objection. Regards, Stephen
pgpQqJbdWI9PU.pgp
Description: OpenPGP digital signature
_______________________________________________ controller-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/controller-dev
