nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Zemerick (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-404) Provide a source build of executables used for Windows or remove functionality
Date Thu, 05 Oct 2017 13:59:00 GMT

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

Jeff Zemerick commented on MINIFI-404:
--------------------------------------

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)

Mime
View raw message