[
https://issues.apache.org/jira/browse/NIFI-10719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625758#comment-17625758
]
Mike R commented on NIFI-10719:
-------------------------------
[~exceptionfactory] thanks. Much appreciated as it gets a bit confusing as to
which ones should be centralized and which ones shouldnt be when I am looking
through them. This will really help a lot!
> Centralize Configuration Versions In The Core POM dependenciesManagement
> -------------------------------------------------------------------------
>
> Key: NIFI-10719
> URL: https://issues.apache.org/jira/browse/NIFI-10719
> Project: Apache NiFi
> Issue Type: Wish
> Affects Versions: 1.18.0
> Reporter: Mike R
> Priority: Major
>
> As mentioned in pull
> [6572|[http://example.com|https://github.com/apache/nifi/pull/6572]] by
> [[email protected]], there are available options to centralize
> management of dependencies in the core POM dependenciesManagement section.
> There are a few of these that would really be helpful such as javax.json-api,
> javax.json, and json-path. It would be great to do 2 things:
> 1) Centralize existing dependencies into the central POM to make things more
> efficient
> 2) Ensure that future processors and new dependencies are integrated with the
> centralized POM as possible. (Might be possible with new documentation and
> review)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
