Mailing-List: contact dev-help@polygene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@polygene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Sun, 04 Jun 2017 11:09:22 +0200
From: Paul Merlin <paulmerlin@apache.org>
To: dev@polygene.apache.org
Subject: Re: yeoman-work back to develop
In-Reply-To: <CADmm+Kc8TeQq9S8sLd1dXYX8nEx7HJDZU0kejVc_NFrF69ST+w@mail.gmail.com>
References: <CADmm+KddwazDMUUvfYXF_tDbinRFaxfzXVYLp-zk1ObzcAYR=w@mail.gmail.com>
 <5932AA7A.2060605@apache.org>
 <CADmm+Kc8TeQq9S8sLd1dXYX8nEx7HJDZU0kejVc_NFrF69ST+w@mail.gmail.com>
Message-ID: <f8360495347bc95348a3b91eb58a1294@nosphere.org>
User-Agent: Roundcube Webmail/1.1.2
archived-at: Sun, 04 Jun 2017 09:09:33 -0000

Le 2017-06-04 02:54, Niclas Hedhman a écrit :
> As for Docker;
> 
> Don't forget that this is code generation and it is EXPECTED that 
> people
> tailor it to their needs. I chose ":latest" so that we don't have to
> constantly maintain the version as those dependencies are likely to 
> upgrade
> faster than we do. It is not important whether the generated project 
> will
> break long-term for using ":latest".

`:latest` could eventually start breaking the day after we release 3.0. 
We do already have the list of qualified docker images in a central 
place. It's like any other dependency. "maintaining" boils down to not 
repeat ourselves.

BTW, it's the same with java dependencies that are also already 
duplicated in the templates. We should reuse those defined in 
~/dependencies.gradle at some point. That can be post 3.0.

> Docker being present is a similar thing. If you don't want Docker, kill 
> the
> DockerRule and change to connect to the external system available 
> through
> other means.
> 
> I think the main point is; We don't need to tailor for all possible
> situations, as generated code is not 'final' in any shape, way or form. 
> But
> perhaps the generator should "check for Docker" and don't generate a
> Dockerrule and disable the test if it is not present.

Well, I get your point but I strongly think that the generated projects 
should not be broken. They are if they fail to build/run. And users will 
think the same way I suppose. The generated projects are just 
scaffoldings yes, but getting started with a broken build (as in not 
building/running) will confuse users and produce noise.