Jonathan Schnéider

The class was renamed to `MeterRegistryCustomizer` in later iterations. We just need to update the sample.

I like the concept, but rather than adding a package level annotation, I think this concept would better fit in our `category` resource concept. Categories are tied to packages so...

I don't see this PR as harmful at any rate, even if we can't fully reproduce. If it solves @zacscoding issue, I think it should be merged without further ado.

i worry about the impact on classloading of `JvmParser`. for now could we avoid the generalization and just create an identical `classpath` method on `KotlinParser.Builder`?

+1 for this feature :)

@EasyAsABC123 can this issue be closed then? It appears to be in master.

Thanks @murdos . For context, in an earlier iteration all recipes were added to one of the regular dependency scopes. And we tried to keep dependencies really thin in rewrite...

Such a great issue for a short live coding talk :). Maybe we should record one together?

I would add that in 10+ simplify to `orElseThrow()`?

https://developer.okta.com/blog/2017/08/09/jax-rs-vs-spring-rest-endpoints