Download JAR files tagged by jersey with all dependencies

Pulls down jackson-jaxrs-json-provider, relocates it, and rewrites its usage of javax.ws.rs classes to make the relocated versions provided by hbase-shaded-jersey. Does NOT include/relocate its entire dependency graph, just performs this isolated transform. This is a separate module because jackson-jaxrs-json-provider is not used universally. At this time, the dependency is required only by hbase-rest.

ZooKeeper REST implementation using Jersey JAX-RS. -------------------------------------------------- This is an implementation of version 2 of the ZooKeeper REST spec. Note: This interface is currently experimental, may change at any time, etc... In general you should be using the Java/C client bindings to access the ZooKeeper server. This REST ZooKeeper gateway is useful because most of the languages have built-in support for working with HTTP based protocols. See SPEC.txt for details on the REST binding.

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

composite REST app - this represents the baseline version that the Connect-Java repository uses for building microservice based REST apps. As they are all Jersey based, there is no real need for Spring or Guice. They always include Tracing, Prometheus, Health checks, Application Lifecycle, easy config injection, Bathe for application start with Service Loader initializers. We are focused on using JIB for Docker generation.

Java client library for the New Relic REST APIs built using Jersey and Gson. The library includes over 110 operations across all of the available 35 New Relic services. It can be used by applications to automate the configuration of New Relic Monitoring, Alerting and Dashboards, but can also be used for extracting incident and metric data, executing Insights queries, and uploading plugin metrics.

The HTTP server module (ks-server-http) implements the Web API of the KnowledgeStore, which includes the two CRUD and SPARQL endpoints. The CRUD Endpoint supports the retrieval and manipulation of semi-structured data about resource, mention, entity and axiom records (encoded in RDF, possibly using JSONLD), and the upload / download of resource representation. The SPARQL Endpoint supports SPARQL SELECT, CONSTRUCT, DESCRIBE and ASK queries according to the W3C SPARQL protocol. The two endpoints are implemented on top of a component implementing the KnowledgeStore Java API (the Store interface), which can be either the the KnowledgeStore frontend (ks-frontend) or the Java Client. The implementation of the module is based on the Jetty Web sever (run in embedded mode) and the Jersey JAX-RS implementation. Reference documentation of the Web API is automatically generated using the Enunciate tool.