com.xpcagey:cagey-config-core

A clean configuration API with dynamic runtime bindings

License	MIT License
Categories	config Application Layer Libs Configuration
GroupId	com.xpcagey
ArtifactId	cagey-config-core
Last Version	1.1.0
Release Date	Sep 26, 2018
Type	jar
Description	A clean configuration API with dynamic runtime bindings

Download cagey-config-core

Filename	Size
cagey-config-core-1.1.0.pom
cagey-config-core-1.1.0.jar	37 KB
cagey-config-core-1.1.0-sources.jar	16 KB
cagey-config-core-1.1.0-javadoc.jar	92 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.xpcagey/cagey-config-core/ -->
<dependency>
    <groupId>com.xpcagey</groupId>
    <artifactId>cagey-config-core</artifactId>
    <version>1.1.0</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.xpcagey/cagey-config-core/
implementation 'com.xpcagey:cagey-config-core:1.1.0'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.xpcagey/cagey-config-core/
implementation ("com.xpcagey:cagey-config-core:1.1.0")

Apache Buildr

'com.xpcagey:cagey-config-core:jar:1.1.0'

Apache Ivy

<dependency org="com.xpcagey" name="cagey-config-core" rev="1.1.0">
  <artifact name="cagey-config-core" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.xpcagey', module='cagey-config-core', version='1.1.0')
)

Scala SBT

libraryDependencies += "com.xpcagey" % "cagey-config-core" % "1.1.0"

Leiningen

[com.xpcagey/cagey-config-core "1.1.0"]

Dependencies

compile (2)

Group / Artifact	Type	Version
com.xpcagey : cagey-config-api	jar	1.1.0
com.xpcagey : cagey-config-spi	jar	1.1.0

test (2)

Group / Artifact	Type	Version
junit : junit	jar	4.12
org.mockito : mockito-core	jar	2.18.3

Project Modules

There are no modules declared in this project.

Cagey Config

This is an abstraction layer for configuration that allows programs to subscribe to value changes and be notified when they occur, permitting live tuning of application logic and automatic stitching of configuration values from multiple sources. It does for configuration what SLF4J has done for logging.

Each application must declare a set of preferences for configuration sources, with each source able to contribute to the parameterization of the next. Configuration sources are each injected by a runtime module that should be placed into the application classpath before running the system. Failure to load a module will not cause the process to fail, but an exception will be thrown to report failures; it is up to the application to decide whether this failure should be considered fatal.

An implementation of the system for static declaration of default values is provided in the core package.

Versions

Version
1.1.0 Sep 26, 2018
1.0.0 Jun 24, 2018