microprofile-config
yaslf4j
microprofile-config | yaslf4j | |
---|---|---|
4 | 1 | |
204 | 1 | |
-0.5% | - | |
6.5 | 1.8 | |
4 months ago | about 1 year ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
microprofile-config
-
slf4j or System.Logger?
There are a lot of great config libraries, you should also take a look at such as smallrye-config. I am trying to make my library compatible with microprofile-config but there are some fundamental differences.
-
Externalized Properties for the JVM
You might have a look at MicroProfile Config as well.
-
JProperties: A modern replacement for java.util.Properties
Now you might be tempted to say well we just need a System.getProperties replacement. A SLF4J of properties config. Perhaps one that uses the ServiceLoader. And indeed microprofile config somewhat solves that problem. The problem is of course is backward compatibility (replacing all the old libraries uses of system properties of which you might not be able to) and of course that config facade adds a dependency.
-
How to create a ConfigSource for Quarkus that knows about existing properties
Quarkus is internally using the SmallRye implementation of Eclipse MicroProfile Config (MP-Config). MP-Config allows to add so called Configuration Sources, that allow to supply config objects in a programmable way from e.g. a file in a strange format or perhaps even from a central repository. This brief post describes how to create a ConfigSource for Quarkus that knows about existing properties
yaslf4j
-
slf4j or System.Logger?
I had the same challenge deciding what option would be the beste and attempted to solve it with an mini library which just attempts slf4j, log4j2 and fallbacks to java itil logging. It was useful for this kind of situation, not quite sure whether it is useful for others though... see here for more https://github.com/Hakky54/yaslf4j
What are some alternatives?
archaius - Library for configuration management API
mdc4spring - Declarative Logging Mapping Diagnostic Context for Spring.
gestalt - A Java configuration library that allows you to build your configurations from multiple sources, merges them and convert them into an easy-to-use typesafe configuration class. A simple but powerful interface allows you to navigate to a path within your configurations and retrieve a configuration object, list, or a primitive value.
config - configuration library for JVM languages using HOCON files
externalized-properties - A lightweight and extensible library to resolve application properties from various external sources.
LogCaptor - 🎯 LogCaptor captures log entries for unit and integration testing purposes
flogger - A Fluent Logging API for Java
jproperties - An efficient, up-to-date reader/writer for Java properties files
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.