The SLFJ4J binding to the JBoss Log Manager is just as it sounds. It’s a SLF4J binding which sends log messages through the JBoss Log Manager. This project is currently used in WildFly and JBoss EAP.
Currently, this supports both SLF4J 2.x and SLF4J 1.7.x. Support for 1.7.x is deprecated and will be removed in future releases.
To use the project you need both SLF4J and JBoss Log Manager on your class path. Then simply add this library and it should be picked up as the SLF4J binding.
See the contributing guide.
Releasing this project requires access to JBoss Nexus.
To perform a release ensure you’re on the correct branch and that branch is up to date. Once everything is setup, you
simply need to run the ./release.sh script. There are two required parameters:
-
-ror--releasewhich is the version you want to release -
-dor--developmentwhich is the next development version.
By default, the release version cannot contain SNAPSHOT and the development version, must contain SNAPSHOT.
./release.sh -r 1.0.0.Final -d 1.0.1.Final-SNAPSHOT| Argument | Requires Value | Description |
|---|---|---|
|
Yes |
The next version for the development cycle. |
|
No |
Forces to allow a SNAPSHOT suffix in release version and not require one for the development version. |
|
N/A |
Displays this help |
|
Unused |
Passes the |
|
Unused |
Passes the |
|
Yes |
The version to be released. Also used for the tag. |
|
No |
Executes the release in as a dry-run. Nothing will be updated or pushed. |
|
No |
Prints verbose output. |
Any additional arguments are considered arguments for the Maven command.