[
https://issues.apache.org/jira/browse/NIFI-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201712#comment-16201712
]
Pierre Villard commented on NIFI-4478:
--------------------------------------
Unless I'm missing something... the Ignite version is defined in the dependency
management of the root pom. It's totally possible to override this version in
the pom of your custom NAR.
Let's say I've:
my-custom-bunble/
-- pom.xml
-- my-custom-nar/
-- my-custom-processor/
And I want to use Ignite 1.7.0. Then, in the pom of the bundle, I can add:
{noformat}
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.apache.ignite</groupId>
<artifactId>ignite-core</artifactId>
<version>1.7.0</version>
</dependency>
</dependencies>
</dependencyManagement>
{noformat}
And then, in the pom of my-custom-processor:
{noformat}
<dependency>
<groupId>org.apache.ignite</groupId>
<artifactId>ignite-core</artifactId>
</dependency>
{noformat}
Let me know if you're trying to do something else... but in any case, it does
not look like a "blocker" to me.
> ignite version should not be mentionned in the root pom.xml
> -----------------------------------------------------------
>
> Key: NIFI-4478
> URL: https://issues.apache.org/jira/browse/NIFI-4478
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.5.0
> Environment: All
> Reporter: Sébastien Bouchex Bellomié
> Priority: Blocker
>
> Root pom.xml is mentioning org.apache.ignite 1.6.0. This prevents from using
> an higher version (2.2.0 for example) in a custom processor.
> org.apache.ignite should only be mentioned in the processor using this
> library.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
