Download JAR files tagged by nifi with all dependencies

This nifi-service-utils module is designed to capture common patterns and utilities that can be leveraged by other services or components to help promote reuse. These patterns may become framework level features or may simply be made available through this utility. It is ok for this module to have dependencies but care should be taken when adding dependencies as this increases the cost of utilizing this module in various nars.

This module removes javax.ws.rs package from jersey-bundle.jar which is used by ranger-plugins-common.jar in order to address javax.ws.rs version mismatch between jersey-bundle.jar and NiFi Registry. NiFi Registry uses javax.ws.rs version 2.1. Without doing this, NiFi Registry encounters java.lang.LinkageError: ClassCastException: attempting to castjar:file:nifi-registry-xxx/work/jetty/nifi-registry-web-api-xxx.war/webapp/WEB-INF/lib/javax.ws.rs-api.jar!/javax/ws/rs/ext/RuntimeDelegate.classtojar:file:/home/koji/nifi-registry-xxx/./ext/ranger/lib/jersey-bundle.jar!/javax/ws/rs/ext/RuntimeDelegate.class

This nifi-prometheus-utils module is designed to capture common patterns and utilities that can be leveraged by components that use Prometheus capabilities to help promote reuse. These patterns may become framework level features or may simply be made available through this utility. It is ok for this module to have dependencies but care should be taken when adding dependencies as this increases the cost of utilizing this module in various nars.

This nifi-processor-utils module is designed to capture common patterns and utilities that can be leveraged by other processors or components to help promote reuse. These patterns may become framework level features or may simply be made available through this utility. It is ok for this module to have dependencies but care should be taken when adding dependencies as this increases the cost of utilizing this module in various nars.

This nifi-utils module should be a general purpose place to store widely and generally useful functions that any component might want to leverage. NO DEPENDENCIES should be added. This module is likely to be leveraged by every extension and should not bring along any other dependencies. The only dependency intended is the nifi-api and even this is expected to be already provided in any case where it would be used. The typical place this util would be found is within a nar and all nars already have nifi-api as a parent dependency. The nifi-api can be thought of as a NiFi Application Container level dependency.