natas_hw
/
slf4j
mirror of https://github.com/qos-ch/slf4j
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
2,058 Commits 13 Branches 104 Tags 17 MiB
Java 99%
HTML 0.9%
Shell 0.1%
Go to file
Hannes Wellmann 2ec7c1034c Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 
This ensures that there is only a single source for OSGi metadata.
Additionally this improves the metadata for some Export-Package entries.

Signed-off-by: Hannes Wellmann <wellmann.hannes1@gmx.net>
 		2023-04-10 00:11:41 +02:00
.github setup-java v3 2022-12-19 20:40:13 +01:00
.idea Change the java indent from 2 to 4. 2021-08-10 19:54:09 +02:00
integration Automate OSGi metadata creation and fix metadata for other slf4j-modules 2023-04-10 00:11:41 +02:00
jcl-over-slf4j Automate OSGi metadata creation and fix metadata for other slf4j-modules 2023-04-10 00:11:41 +02:00
jul-to-slf4j Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
log4j-over-slf4j Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
osgi-over-slf4j Automate OSGi metadata creation and fix metadata for other slf4j-modules 2023-04-10 00:11:41 +02:00
slf4j-api start work on 2.0.8-SNAPSHOT 2023-03-17 20:41:07 +01:00
slf4j-ext Automate OSGi metadata creation and fix metadata for other slf4j-modules 2023-04-10 00:11:41 +02:00
slf4j-jdk-platform-logging Automate OSGi metadata creation and fix metadata for other slf4j-modules 2023-04-10 00:11:41 +02:00
slf4j-jdk14 Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
slf4j-log4j12 start work on 2.0.8-SNAPSHOT 2023-03-17 20:41:07 +01:00
slf4j-migrator start work on 2.0.8-SNAPSHOT 2023-03-17 20:41:07 +01:00
slf4j-nop Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
slf4j-reload4j Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
slf4j-simple Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
src/main skip assembly 2021-08-10 19:54:11 +02:00
.gitattributes Add git attributes 2014-09-26 23:33:52 -04:00
.gitignore add mac os x metadata file .DS_Store to .gitignore 2013-03-27 03:13:34 +04:00
.travis.yml add travis build cache 2021-08-16 16:12:45 +02:00
FUNDING.yml add FUNDING.yml file 2022-01-04 15:03:13 +01:00
LICENSE.txt add slf4j-reload4j module 2022-01-13 15:21:26 +01:00
README.md edit blurb on release championing 2022-10-11 21:18:58 +02:00
SECURITY.md upodate gpg key information 2022-08-20 21:56:31 +02:00
codeStyle.xml Reformat all code with the exception of the slf4j-android module to use 4 space indentation and max line width of 160. 2015-03-26 12:59:25 +01:00
pom.xml Replace all remaining OSGi MANIFEST.MF by bundle-plugin instructions 2023-04-10 00:11:41 +02:00
release.sh add reminder in release.sh 2022-08-22 15:01:50 +02:00

README.md

About SLF4J

The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, reload4j, log4j 2.x) allowing the end user to plug in the desired logging framework at deployment time.

More information can be found on the SLF4J website.

Build Status

Build Status

Search org.slf4j artifacts on Maven Central

Maven Central

In case of problems

In case of problems please do not hesitate to post an e-mail message on the slf4j-user@qos.ch mailing list. However, please do not directly e-mail SLF4J developers. The answer to your question might be useful to other users. Moreover, there are many knowledgeable users on the slf4j-user mailing lists who can quickly answer your questions.

Urgent issues

For urgent issues do not hesitate to champion a release. In principle, most championed issues are solved within 3 business days ensued by a release.

How to build SLF4J

SLF4J uses Maven as its build tool.

SLF4J version 2.0.x will run under Java 8 but requires Java 9 or later to build.

How to contribute pull requests

If you are interested in improving SLF4J, that is great! The SLF4J community looks forward to your contribution. Please follow this process:

  1. Start a discussion on the slf4j-dev mailing list about your proposed change. Alternately, file a bug report to initiate the discussion. Note that we ask pull requests to be linked to a Jira ticket.

  2. Fork qos-ch/slf4j. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back.

  3. Make your changes on the branch you hopefully created in Step 2. Be sure that your code passes existing unit tests. Please add unit tests for your work if appropriate. It usually is.

  4. All commits must have signed off by the contributor attesting to Developer Certificate of Origin (DCO). Commits without sign off will be automatically rejected by the DCO GitHub check application.

  5. Push your changes to your fork/branch in GitHub. Don't push it to your master! If you do it will make it harder to submit new changes later.

  6. Submit a pull request to SLF4J from your commit page on GitHub.

  7. Did we mention that you will be asked to link your pull request with a Jira ticket?