nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aldrin Piri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-436) Consider common dependency management with NiFi
Date Tue, 30 Jan 2018 16:14:00 GMT

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

Aldrin Piri commented on MINIFI-436:
------------------------------------

I linked this to MINIFI-422 because I think that is likely precludes this but agree that it
is an issue that needs to be addressed

> Consider common dependency management with NiFi
> -----------------------------------------------
>
>                 Key: MINIFI-436
>                 URL: https://issues.apache.org/jira/browse/MINIFI-436
>             Project: Apache NiFi MiNiFi
>          Issue Type: Improvement
>          Components: Build
>            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
(v7.6.3#76005)

Mime
View raw message