nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Bean <>
Subject dependency scope
Date Fri, 11 Oct 2019 16:22:03 GMT
We are building Apache NiFi on a separate network with an internal Nexus
repository. When I attempt to build the rel/nifi-1.9.2 tag, I get
compilation errors due to an import failing. Specifically, it is (and CacheBulider)
in nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/

These classes are part of I ran a 'mvn
from nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core.
It shows:
[INFO] +- com.fasterxml.jackson.core:jackson-core:jar:2.9.7:compile
[INFO] +- org.apache.curator:curator-test:jar:2.9.1:test
[INFO] |  +- org.javassist:javassist:jar:3.18.1-GA:compile
[INFO] |  +- org.apache.commons:commons-math:jar:2.2:test
[INFO] |  \-

Note the scope of "test" for guava.

However, when I build the same dependency tree on an Internet-connected
system, I get a scope of "compile" on

I checked the parent dependency,
com.fasterxml.jackson.core:jackson-core:2.9.7 pom file. It does not
explicitly have a scope of test.
Both the guava and jackson-core JAR files are identical between the two

Can someone explain why the scope is different? Is there something in one
of nifi's pom's that is assumed when it should be explicit?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message