You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Ferenc Gerlits (Jira)" <ji...@apache.org> on 2021/02/02 16:31:00 UTC

[jira] [Updated] (MINIFICPP-1472) 1. Separate API and utility libraries from minifi-core

     [ https://issues.apache.org/jira/browse/MINIFICPP-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ferenc Gerlits updated MINIFICPP-1472:
--------------------------------------
    Summary: 1. Separate API and utility libraries from minifi-core  (was: Separate API and utility libraries from minifi-core)

> 1. Separate API and utility libraries from minifi-core
> ------------------------------------------------------
>
>                 Key: MINIFICPP-1472
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1472
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Ferenc Gerlits
>            Priority: Minor
>
> Currently, extensions depend on {{minifi-core}}, which contains (almost) everything under {{libminifi}}.[1]
> We should separate out a {{minifi-extension-api}} library and a {{minifi-extension-utils}} library, and make sure only these are used by the extensions (and leave the rest in {{minifi-core}}).  The idea is that
>  * the {{api}} library would be stable (can only be broken at major releases);
>  * the {{utils}} library is mainly aimed at our own extensions, and it could change at each release – but users are free to use it if they are willing to recompile for every release.
> For this step, the new libraries can remain static.
> TODO: this task may need to be broken down further.
>  
> [1] the one thing it doesn't is {{ProcessorUtils}}, for no clear reason (probably history); that can be moved inside {{minifi-core}} as the first step of this task



--
This message was sent by Atlassian Jira
(v8.3.4#803005)