service-enabled / dropwizard-request-tracker Goto Github PK

I tried building against Dropwizard 1.3.7 just to see what would happen.

It looks like Guava Supplier now just proxies to java.util.function.Supplier, which doesn't exist in Java 7. That's a problem since we set our compiler source and target 1.7. Changing source and target to 1.8 fixed the problem, but I was using JDK 9 and ran into a series of runtime dependency issues. I'm guessing none of this is a problem for users. Still, passing builds for development seems important.

Maybe it's time for a general refresh.

Here's my thoughts:

1. Build against Dropwizard 1.3.7
2. Target Java 8
3. Update any massively outdated dependencies
4. Replace any resulting deprecations
5. Ensure builds using Java 9-11 work without error

This would be a new major version.

I've got a branch started with some of the changes already.

Update poms to follow semantic versioning, ie we're not prod ready so we should be 0.0.1

The most recently published version available in maven central is 0.2.0, which is aimed at dropwizard 0.7.1

It looks like the current version is aimed at dropwizard 0.9.1 - could this please be published to maven central?

Once the bundle is complete we can probably publish to maven central. Never done that, no idea how to.

Split from #33.

See my comment which discusses some of JUnit 5 and dropwizard.

The tricky part will be the removal of rules. Since we wrap one rule with another rule. Need to figure out how to do that with extensions.

This will have to be built on top of #34 since JUnit 5 requires Java 8.

Test with two services calling each other.