Yes, it's reasonable to build an uber-jar in development, using Maven/Ivy to resolve dependencies (and of course excluding 'provided' dependencies like Spark), and push that to production. That gives you a static artifact to run that does not depend on external repo access in production.
On Wed, Oct 21, 2020 at 1:15 PM Wim Van Leuven < wim.vanleu...@highestpoint.biz> wrote: > I like an artefact repo as the proper solution. Problem with environments > that haven't yet fully embraced devops: artefact repos are considered > development tools and are often not yet used to promote packages to > production, air gapped if necessary. > -wim >
