You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Andrew Christianson (JIRA)" <ji...@apache.org> on 2017/03/22 13:58:41 UTC
[jira] [Commented] (MINIFI-213) Move dependencies to
ExternalProject
[ https://issues.apache.org/jira/browse/MINIFI-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936353#comment-15936353 ]
Andrew Christianson commented on MINIFI-213:
--------------------------------------------
Have we considered using git submodules for this? It would free us from having to hold copies of all the third-party code, yet would enable a full recursive clone for embedded or offline compiling. It also simplifies maintenance when it comes to updating third-party dependencies (i.e. update the submodule reference to a new upstream tag/commit), although it would add some complexity in other cases. Something to consider.
> 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)