[
https://issues.apache.org/jira/browse/NIFI-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-8569.
--------------------------------
Resolution: Won't Do
[~pvillard] I think this ticket is invalid at this point given that MiNiFi Java
was merged into core. Reopen if you disagree.
> Consider common dependency management with NiFi
> -----------------------------------------------
>
> Key: NIFI-8569
> URL: https://issues.apache.org/jira/browse/NIFI-8569
> Project: Apache NiFi
> Issue Type: Improvement
> Components: MiNiFi
> Reporter: Pierre Villard
> Priority: Major
>
> In order to avoid problems raised in MINIFI-431 and MINIFI-435 it could be
> interesting to consider a common dependency management between MiNiFi Java
> and NiFi projects. This would prevent dependency conflicts when common
> dependencies are upgraded on only one side.
> Not sure what's the best solution is while ensuring proper CI builds. An
> option could be to use the main pom of NiFi project as parent pom of the
> MiNiFi project with the version of NiFi that is used to build MiNiFi (not the
> SNAPSHOT version though). This way, common dependencies could be defined only
> on NiFi's side. The release process would need to be changed a bit to ensure
> version of parent pom is correctly updated to the least released version of
> NiFi.
> To be discussed here.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
