Rubix provided libraries

Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases

Essential knowledge

Changed on:

24 Mar 2026

Overview

This document provides a list of dependencies provided by released Rubix versions. Plugin developers can use these dependecies in their OSGi bundles and should embed additional dependencies if required. Embeding custom versions of provided dependencies is not recomended.

Key points

An OSGi container modular framework overview
List of libraries and versions provided by the Rubix OSGi runtime

OSGi Container Framework

An OSGi container is a modular framework for Java that facilitates the development and management of applications composed of interconnected components called bundles. It provides a dynamic runtime environment where bundles can be installed, updated, and removed without restarting the entire application. The container manages dependencies by maintaining a registry of available services and ensuring that bundles can access the resources they need while adhering to versioning and compatibility constraints.

List of common Rubix Runtime Libraries

Package `com.fasterxml.jackson.core` Version: `2.15.0`
- `jackson-core`
- `jackson-annotations`
- `jackson-databind`
Package `com.fasterxml.jackson.datatype` Version: `2.8.3`
- `jackson-datatype-guava`
Package `com.fasterxml.jackson.jaxrs` Version: `2.15.0`
- `jackson-jaxrs-base`
- `jackson-jaxrs-json-provider`
Package `com.fasterxml.jackson.dataformat` Version: `2.15.0`
- `jackson-dataformat-cbor`
Package `org.apache.commons` Version: `3.4`
- `commons-lang3`
Package `commons-io` Version: `2.2`
- `commons-io`
Package `com.google.guava` Version: `19.0`
- `guava`
Package `org.apache.httpcomponents` Version: `4.4.16`
- `httpcore-osgi`
- `httpclient-osgi`
Package `io.netty` Version: `4.1.125.Final`
- `netty-codec-http`
- `netty-common`
- `netty-buffer`
- `netty-codec`
- `netty-handler`
- `netty-resolver`
- `netty-transport`
- `netty-transport-native-unix-common`

OSGi related bundle installation failures | osgi.wiring.package

When bundle installation fails with errors like

`Unable to resolve <ACCOUNT>.<module> : missing requirement [<ACCOUNT>.<module> <VERSION>] osgi.wiring.package; Additional package information`
`Unresolved requirements: [[<ACCOUNT>.<module> <VERSION>] osgi.wiring.package; Additional package information`

Such error are usually caused by `pom.xml` file containing a dependency, and subsequently an import statement, that is not satisfied by either Rubix runtime or module's own embeded dependencies.If dependency is unique to the module and isn't provided by Rubix runtime, then module need to embed such dependency.When using a more recent version of included dependency that is not provided by Rubix in runtime then there are two options:

Downgrade their version to provided, as long as they are not using any features introduced between newer and provided version.
Customer could embed their version within the bundle so it is not exposed outside the bundle. However, this approach is also not ideal, as it defeats the purpose of having reusable bundles in Rubix and makes individual bundles heavier, potentially increasing memory usage.

Embedding a custom library and import in OSGi

To properly embed a custom library in your plugin, ensure the following conditions are met:

Use an appropriate Maven scope for the dependency. Typically, `compile` or `runtime` scope is required for embedding. Avoid using `provided`, as those dependencies are not included in the final artifact.
Ensure the dependency is actually embedded in the final plugin JAR after the Maven build completes. You can verify this by extracting the generated JAR and checking that the dependency classes are present.
Check the `Import-Package` header in the `MANIFEST.MF` file. Ideally, packages from embedded libraries should not appear there. If they do, it means the bundle is still expecting them to be provided externally.
Avoid exporting packages from embedded libraries as well

Your plugin’s `pom.xml` should already include the following configuration for the Maven Bundle Plugin to enable embedding:

`
`

<Embed-Dependency>*;scope=compile|runtime;inline=true</Embed-Dependency>
<Embed-Transitive>true</Embed-Transitive>
<Bundle-ClassPath>.,{maven-dependencies}</Bundle-ClassPath>If you still see your dependency packages listed under the `Import-Package` directive, you can instruct the Maven Bundle Plugin to treat them as private by adding:`<Private-Package>com.your.private.package.*</Private-Package>`This ensures the packages are included in the bundle and not imported from external sources.

Rubix provided libraries

Overview

Key points

OSGi Container Framework

List of common Rubix Runtime Libraries

Related content

Getting Started with the Utility Bundles

Upgrade an Existing Plugin to the latest SDK

Module Recipe - Plugin Setup and Installation Guide

Building Blocks

Browse By Type

Helpful Resources

Quick Links