Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 04E3B200D15 for ; Thu, 5 Oct 2017 16:00:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 02F641609E1; Thu, 5 Oct 2017 14:00:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 48E601609DA for ; Thu, 5 Oct 2017 16:00:09 +0200 (CEST) Received: (qmail 75413 invoked by uid 500); 5 Oct 2017 14:00:08 -0000 Mailing-List: contact commits-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 commits@nifi.apache.org Received: (qmail 75403 invoked by uid 99); 5 Oct 2017 14:00:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Oct 2017 14:00:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 803F81808B3 for ; Thu, 5 Oct 2017 14:00:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id e9fMgrJJ2GUO for ; Thu, 5 Oct 2017 14:00:06 +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 9E36A5F613 for ; Thu, 5 Oct 2017 14:00:05 +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 D59A7E00C7 for ; Thu, 5 Oct 2017 14:00:04 +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 8E9E1242FF for ; Thu, 5 Oct 2017 14:00:04 +0000 (UTC) Date: Thu, 5 Oct 2017 14:00:04 +0000 (UTC) From: "Jeff Zemerick (JIRA)" To: commits@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MINIFI-404) Provide a source build of executables used for Windows or remove functionality MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 05 Oct 2017 14:00:10 -0000 [ https://issues.apache.org/jira/browse/MINIFI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192907#comment-16192907 ] Jeff Zemerick edited comment on MINIFI-404 at 10/5/17 1:59 PM: --------------------------------------------------------------- Looking at Tomcat, the commons daemon dependencies are downloaded [1] by the build into user.home/tomcat-build-libs/commons-daemon-version [2]. The executables are then copied (and renamed appropriately) to the build's bin directory [3]. This keeps the executables out of the source by downloading them at build time. Could we do something like that? [1] https://github.com/apache/tomcat/blob/trunk/build.xml#L2623 [2] https://github.com/apache/tomcat/blob/trunk/build.properties.default#L151 [3] https://github.com/apache/tomcat/blob/trunk/build.xml#L1739 was (Author: jzemerick): Looking at Tomcat, the commons daemon dependencies are downloaded [1] by the build into ${user.home}/tomcat-build-libs/commons-daemon-${commons-daemon.version} [2]. The executables are then copied (and renamed appropriately) to the build's bin directory [3]. This keeps the executables out of the source by downloading them at build time. Could we do something like that? [1] https://github.com/apache/tomcat/blob/trunk/build.xml#L2623 [2] https://github.com/apache/tomcat/blob/trunk/build.properties.default#L151 [3] https://github.com/apache/tomcat/blob/trunk/build.xml#L1739 > Provide a source build of executables used for Windows or remove functionality > ------------------------------------------------------------------------------ > > Key: MINIFI-404 > URL: https://issues.apache.org/jira/browse/MINIFI-404 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Agent Configuration/Installation > Affects Versions: 0.2.0 > Reporter: Aldrin Piri > Priority: Blocker > Fix For: 0.3.0 > > > MINIFI-344 provided windows support making use of the Apache Daemon procrun. This was accomplished by making use of those binaries and wrapping the application which is an issue for a proper source release. We need to determine a way to generate these at build time (other Apache projects generate such artifacts and we should evaluate how those are accomplished). Should no tenable solution be found before our next release, this will have to be removed until a time when we are able to. In such a scenario, we could capture this information in docs for those that are interested in doing so out of the community processes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)