You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "marco polo (JIRA)" <ji...@apache.org> on 2017/03/22 14:02:41 UTC
[jira] [Comment Edited] (MINIFI-213) Move dependencies to
ExternalProject
[ https://issues.apache.org/jira/browse/MINIFI-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936359#comment-15936359 ]
marco polo edited comment on MINIFI-213 at 3/22/17 2:01 PM:
------------------------------------------------------------
I usually use a git submodule when pulling ExternalProjects, but there are some cases for deps that don't have a git repo or those that delete tags ( I had this with a Pivotal Repo ), which require download.
When I said download dependencies I was including things like boost, which you can do with a variety of cmake dep managers.
was (Author: phrocker):
I usually use a git submodule when pulling ExternalProjects, but there are some cases for deps that don't have a git repo or those that delete tags ( I had this with a Pivotal Repo ), which require download.
> Move dependencies to ExternalProject
> ------------------------------------
>
> Key: MINIFI-213
> URL: https://issues.apache.org/jira/browse/MINIFI-213
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Reporter: marco polo
>
> Could we move the libs in thirdparty to ExternalProject inclusions that download the dependencies? Would this cause an impact to any users?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)