Hi Natalie, sorry for the late reply. :-)
> I’m curious about where you all think might be a good home for that new > library though. The current ideas, in order of which I currently prefer: > * A new standalone library > * A sub module of metrics > * a sub module of Dropwizard-health I think a standalone library makes sense if the goal is for it to be used in other projects than dropwizard-health or Dropwizard in general. You're welcome to start it under the umbrella of the Dropwizard organization on GitHub, if you want to go that route. In general, I think it would also make sense to move dropwizard-health as a core module into Dropwizard, so that people don't have to discover it independently. So we'd have the standalone library for the framework-independent parts and dropwizard-health as a core module in Dropwizard. What do you think? Best regards, Jochen > Hi folks! > > Awhile back we contributed the dropwizard-health module, which offers some > extra functionality for health checks in the Dropwizard framework. I’ve been > wanting to separate out the core logic of that library from the Dropwizard > glue, similar to the metrics library, because much of it is very framework > agnostic, and generally useful. > > I’m curious about where you all think might be a good home for that new > library though. The current ideas, in order of which I currently prefer: > * A new standalone library > * A sub module of metrics > * a sub module of Dropwizard-health > > Any thoughts on this? I want the DW glue to remain in the same library, so > that won’t change. > > Thanks! -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-dev/676A0166-5DF3-45D3-A4DC-9BD91600BB76%40schalanda.name.
