Story
As a Galasa user in an organisation with a restricted network environment, I want to be able to use galasactl in an offline mode, so that it doesn't attempt to contact Maven for dependencies during execution.
Background
When running galasactl runs submit local, the spawned JVM attempts to download dependencies at runtime from the --remotemaven URL. Even when --localMaven is specified, the runtime still falls back to --remotemaven for any artifact not found locally.
An enhancement to galasactl to create an offline/fat-JAR execution mode where all dependencies are resolved and bundled at build time would eliminate runtime Maven resolution entirely and fix this issue.
Tasks
Story
As a Galasa user in an organisation with a restricted network environment, I want to be able to use
galasactlin an offline mode, so that it doesn't attempt to contact Maven for dependencies during execution.Background
When running
galasactl runs submit local, the spawned JVM attempts to download dependencies at runtime from the--remotemavenURL. Even when--localMavenis specified, the runtime still falls back to--remotemavenfor any artifact not found locally.An enhancement to
galasactlto create an offline/fat-JAR execution mode where all dependencies are resolved and bundled at build time would eliminate runtime Maven resolution entirely and fix this issue.Tasks