Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Thu, 12 Jan 2017 10:10:52 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.13034216.1484214335000.917.1484215852165@Atlassian.JIRA>
In-Reply-To: <JIRA.13034216.1484214335000@Atlassian.JIRA>
References: <JIRA.13034216.1484214335000@Atlassian.JIRA> <JIRA.13034216.1484214335553@arcas>
Subject: [jira] [Commented] (FLINK-5466) Make production environment default
 in gulpfile
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 12 Jan 2017 10:10:53 -0000


    [ https://issues.apache.org/jira/browse/FLINK-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820648#comment-15820648 ] 

ASF GitHub Bot commented on FLINK-5466:
---------------------------------------

Github user joerg84 commented on the issue:

    https://github.com/apache/flink/pull/3100
  
    LGTM, thanks for fixing this!


> Make production environment default in gulpfile
> -----------------------------------------------
>
>                 Key: FLINK-5466
>                 URL: https://issues.apache.org/jira/browse/FLINK-5466
>             Project: Flink
>          Issue Type: Improvement
>          Components: Webfrontend
>    Affects Versions: 1.2.0, 1.1.4
>            Reporter: Ufuk Celebi
>
> Currently the default environment set in our gulpfile is development, which lead to very large created JS files. When building the web UI we apparently forgot to set the environment to production (build via gulp production).
> Since this is likely to occur again, we should make the default environment production and make sure to use development manually.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)