Three tasks: upgrade and use latest gradle plugin features, improve DockerFile performance, wrap runtime exceptions

[dmgaldi]

Overview

• Upgrade user service to use gradle plugin for RAML generation
• Upgrade container core version to the latest
• Refine Dockerfile task ordering to improve cache hit %
• (Java code) Add exception wrappers around service domain logic to hide internals on 500s

Note: the makefile is now unnecessary, but is often convenient for development (no longer used in Dockerfile)

Testing

• Ran gradle tasks successfully
• Created docker image successfully

[dmgaldi]

I'm not actually sure I like this way better. Harder to track what all is going on. Like if I run make gen-jaxrs, I can track each step along the way. But by tacking on pre- and post-conditions to a "well known" gradle target, it could be a total mystery how it happens to someone not in the know.

Do you think we should have a gradle plugin task for fetching the RAML? I was hesitant since it's only done in EDA at the moment. I'm not sure how one would "opt into", "opt out of" or configure the common RAML fetch task if we put it in the plugin.

[dmgaldi]

I'm not actually sure I like this way better. Harder to track what all is going on. Like if I run make gen-jaxrs, I can track each step along the way. But by tacking on pre- and post-conditions to a "well known" gradle target, it could be a total mystery how it happens to someone not in the know.

Do you think we should have a gradle plugin task for fetching the RAML? I was hesitant since it's only done in EDA at the moment. I'm not sure how one would "opt into", "opt out of" or configure the common RAML fetch task if we put it in the plugin.

Talked about this after scrum, updated based on our conversation and Ellie's help

[ryanrdoherty]

@dmgaldi @Foxcapades Can you take a look at this as a final cut? I think it's ready to merge; can maybe be a template to improve all the other services (esp EDA services).

[ryanrdoherty]

@steve-fischer-200 Please review the Java code