You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Pierre Villard (JIRA)" <ji...@apache.org> on 2018/01/29 08:16:00 UTC

[jira] [Created] (MINIFI-436) Consider common dependency management with NiFi

Pierre Villard created MINIFI-436:
-------------------------------------

             Summary: 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


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)