From issues-return-19138-apmail-nifi-issues-archive=nifi.apache.org@nifi.apache.org Fri Feb 3 08:02:58 2017 Return-Path: X-Original-To: apmail-nifi-issues-archive@minotaur.apache.org Delivered-To: apmail-nifi-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 68CD4192C3 for ; Fri, 3 Feb 2017 08:02:58 +0000 (UTC) Received: (qmail 20531 invoked by uid 500); 3 Feb 2017 08:02:58 -0000 Delivered-To: apmail-nifi-issues-archive@nifi.apache.org Received: (qmail 20498 invoked by uid 500); 3 Feb 2017 08:02:58 -0000 Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list issues@nifi.apache.org Received: (qmail 20489 invoked by uid 99); 3 Feb 2017 08:02:58 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2017 08:02:58 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E54E8C05E9 for ; Fri, 3 Feb 2017 08:02:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id T6s2I6hmgYMA for ; Fri, 3 Feb 2017 08:02:57 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 765ED5FB73 for ; Fri, 3 Feb 2017 08:02:56 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 0BC83E0146 for ; Fri, 3 Feb 2017 08:02:51 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9B94025286 for ; Fri, 3 Feb 2017 08:02:51 +0000 (UTC) Date: Fri, 3 Feb 2017 08:02:51 +0000 (UTC) From: "Andre (JIRA)" To: issues@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-3434) nifi-assembly dependencies should allow users to skip the creation of ZIP and TAR.GZ packages MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851203#comment-15851203 ] Andre commented on NIFI-3434: ----------------------------- from list: I think this could be useful. Only caveat is that I'm sure there are folks in the community that have automated processes that make use of these binaries. >From the dev standpoint, I could see a profile that disables the assembly from happening such that the build occurs as it does now unless folks explicitly want to avoid it. Regardless of implementation, can see why it would be helpful. > nifi-assembly dependencies should allow users to skip the creation of ZIP and TAR.GZ packages > --------------------------------------------------------------------------------------------- > > Key: NIFI-3434 > URL: https://issues.apache.org/jira/browse/NIFI-3434 > Project: Apache NiFi > Issue Type: Improvement > Affects Versions: 1.1.1 > Reporter: Andre > Assignee: Andre > > devs, > Currently calling 'mvn clean install' creates a ZIP, a TAR.GZ and a > directory containing the same code. This leads to wasted disk space and a > lot of wasted disk writes (something that a lot of folks using SSDs prefer > to avoid). > Would anyone oppose the idea of moving the ZIP and TAR.GZ assemblies into a > "release" profile (or whatever name we agree to). This way we could > maintain the directory "format" (which I suspect most of us use during > development), while still providing a convenient way of creating the ZIP > and TAR.GZ packages. -- This message was sent by Atlassian JIRA (v6.3.15#6346)