Tobias Bocanegra commented on JCRVLT-275:

I don't see a point of distributing a developer CLI tool on a docker image. 
every developer sets up his machine according to his needs. java version, scm 
tools, os, console, ide, all vary based on personal preferences and company 

the binary of the vault client can already be downloaded from the maven 
repositories, eg:

> Docker build and docker image for filevault
> -------------------------------------------
>                 Key: JCRVLT-275
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-275
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: Packaging, vlt
>    Affects Versions: 3.1.42
>            Reporter: Ioan Eugen Stan
>            Priority: Major
> I believe it will improve FileVault usage if we make it easier for users to 
> consume the software.
> One way to achieve this is to publlish binary artifacts.
> Docker makes this easy to.
> I've published patches in a PR on Github 
> [https://github.com/apache/jackrabbit-filevault/pull/25] .
> Docker file contains a multi-stage docker build:
> Stage 1: builds FileVault binary using official maven openjdk image
> Stage 2: Creates a FileVault image that can be published via automated builds 
> on docker hub.

This message was sent by Atlassian JIRA

Reply via email to