Limbus API · This module only contains interfaces that are needed to develop plugins for the Limbus Engine.
Group: com.remondis.limbus - All Dependencies
Limbus Utils · Commonly used utils for Limbus development and plugin or extension development.
Limbus Staging · This is a library for integration test development. This library enables Limbus Plugin developers to simulate a Limbus Engine Environment, deploy their Plugin classes and assert their behaviour. The class com.remondis.limbus.launcher.LimbusStaging is the entry point for this library. The features can be used in a fluent builder style.
Limbus Showcase Launcher · This module is an example on how to start an instance of Max5 Limbus Engine and how to deploy artifacts on it. Use the launcher class to start the example. Note: This project is the host for a Limbus Engine. Therefore the dependency to limbus-engine-impl is needed. If you just want to develop a Limbus Plugin the dependency limbus-engine-api only is needed.
Limbus JDK Logging Activator · This logging activator configures the Java JUL to be used by the Limbus Engine.
Limbus JSSE · This module provides a way to setup JSSE via Limbus configuration.
Limbus Dependency Management for Plugins · Limbus dependency management POM for plugin developers. This POM imports the dependency management for Limbus plugin development libraries. Several scopes are predefined, do not override scope without knowing what you do. Example: Do not set the limbus-engine-api into scope "compile". This will make the plugin unusable on the Limbus Engine!
Limbus System · The Limbus System is a small light-weight CDI framework managing the Limbus Core Components. The object graph is represented by an XML configuration file or can be build using the Limbus System API. This module delivers an optional system component that visualizes the object graph and its dependencies after initializing: com.remondis.limbus.system.visualize.LimbusSystemVisualizer This component can be added to the Limbus System. To keep the dependencies of this module transparent and light-weight, the graph renderer is declared as an optional dependency. Add the following dependencies to your project to use the visualisation component: <!-- Graph Stream for Visualization feature This is an optional dependency and only required if using the com.remondis.limbus.system.visualize.LimbusSystemVisualizer --> <dependency> <groupId>org.graphstream</groupId> <artifactId>gs-core</artifactId> <version>1.3</version> </dependency> <dependency> <groupId>org.graphstream</groupId> <artifactId>gs-ui</artifactId> <version>1.3</version> </dependency>
Limbus Plugin Showcase · This module is an example on how to implement a Limbus plugin.
Limbus Properties · A property wrapper with extended features.
Limbus Monitoring · API to create and process monitoring information using extendable interfaces for consumers and producers.
Limbus Launcher · A small framework for running abstract engines. Provides bootstrap and shutdown sequences and thread cleaning features for controlled termination.
Limbus Event Multicaster · Module for a datastructure that allows to multicast method invocations to subscribers.
Limbus Engine Interfaces · This module defines the public interfaces introduced by the Limbus Engine environment.
Limbus Engine Implementation · This is the Max5 Limbus Engine implementation that currently provides the following features: - Hot-Deploy features: - Deploy from filesystem - Deploy via Limbus API - Deploy via filesystem observer - Deploy from Maven Repositorx - Undeploy via Limbus API - Plugin lifecycle support - Classloader hierarchy - Isolation of deployed classpaths - Shared classloader for centralized libraries - Maintenance console with linux terminal suppot - Safety shutdown sequence - Classloading leak prevention - Thread stopping and cleaning
Limbus System API · Provides the neccessary interfaces to use Limbus System.
Limbus Maven Integration · This library provides a service implementation to resolve, download and provide Maven artifacts from remote/local repositories. This library uses Aether and Maven dependencies that are based on Java 8. Because the projects were terminated and Maven developers announced that no compatibility for Java 9 is planned, this service must be deployed on the legacy Java < 9 class path.