To my knowledge, no one has started a junit5 module. It'd probably be best
if it was started outside the main repo to allow for experimentation and
then users can choose to include it as a third party module
On Monday, August 8, 2016 at 1:27:47 PM UTC-4, Trevor Mack wrote:
>
> Happy Monday
It looks like logback was just updated (
https://github.com/dropwizard/dropwizard/pull/1918) so I feel like this
problem is feasible to solve now. :)
On Tuesday, February 7, 2017 at 9:33:12 PM UTC-5, Evan Meagher wrote:
>
> Good call. Thanks, Nick.
>
> I see you've already slapped it on #1686,
I believe there is a currently outstanding issue for tracking this
bug/feature: https://github.com/dropwizard/dropwizard/issues/1404
On Tuesday, February 14, 2017 at 9:00:07 AM UTC-5, HAL2000 wrote:
>
> Hi,
>
> I need to rotate or backup the current log file on startup but can't work
> out how
Hey Josh,
I don't know if there is a right way, per se, I just have intellij open the
top level pom file and everything is imported fine. I do not use the
"import project" functionality.
Thanks,
Nick.
On Wednesday, February 8, 2017 at 3:52:23 PM UTC-5, Josh Rehman wrote:
>
> Hello!
>
> Happy
I am very pleased with my setup where I store metrics in graphite but use
grafana for visualizations.
On Wednesday, May 17, 2017 at 8:30:33 AM UTC-4, srumith u wrote:
>
> Hi Guys
>
> I am trying to give some web user interface to the dropwizard metrics.
> Checked Graphite and Ganglia but I
Right, yeah I held off documenting guava removal as it hasn't been entirely
removed from all aspects of Dropwizard (eg: it's still a core dependency),
and it's up in the air if it will be completely removed (ie: someone has to
put in the work to see how viable it is).
It would be interesting
Hey all,
While all the features / changes slotted and a date for Dropwizard 2.0 is
yet to be finalized, I've created the 1.3 to 2.0 migration guide for all
potentially breaking changes:
https://github.com/dropwizard/dropwizard/wiki/Upgrade-guide-1.3.x-to-2.0.x
Feel free help out in any way or
Hey Michael and Peter, welcome!
I recommend that any generic extensions that you've written be made into
Dropwizard bundles (like dropwizard-graphql:
https://github.com/smoketurner/dropwizard-graphql). This'll be the quickest
way to sharing extensions and receiving feedback as you won't need
While I'd prefer and wait until after 2.0 is out before including them into
dropwizard, these modules seem well thought out: finer grained healthchecks
with the ability to have them cached, and deeper support for HTTP headers
seem great!
How backwards compatible are these changes?
Are you
