Possible enhancement: expand install_jar() options for CI/CD pipelines #541
Description
This came up when working with docker-based images and thinking of how they can be used in CI/CD pipelines. These pipelines are great for consistency since you always start with a blank slate - but that means you have to figure out how to get a fresh copy of everything you need.
The most obvious choice is maven coordinates instead of an explicit file. This is standardized and the backend can either call maven in a subshell or use the appropriate library directly. With custom docker images it's also possible to cheat by having the docker image download these dependencies and later the backend can find the files via the filename conventions.
A second option is os packages. These are common and install the jars to /usr/share/java, so again we could have the docker image install these dependencies and later the backend can look for the jars at the standard location.
I'm sure there's other possibilities. I just wanted to toss out a few ideas since it's become so common to use CI/CD for rapid deployments on new instances. Not just docker, of course, but that's a good starting point.