maven-simple VS Logback

dependencyResolutionManagement { repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS) repositories { //... jcenter() maven { url 'https://jitpack.io' } } }

pluginManagement { repositories { google() mavenCentral() gradlePluginPortal() } } dependencyResolutionManagement { repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS) repositories { google() mavenCentral() maven() { url "https://jitpack.io" } } } rootProject.name = "[App name here]" include ':app'

plugins { id 'com.android.application' version '8.0.1' apply false id 'com.android.library' version '8.0.1' apply false id 'org.jetbrains.kotlin.android' version '1.8.20' apply false } allprojects { repositories { google() maven { url "https://jitpack.io" } mavenCentral() } } dependencies { implementation 'com.github.yausername.youtubedl-android:library:-SNAPSHOT' implementation 'com.github.yausername.youtubedl-android:ffmpeg:-SNAPSHOT' }

gradle was updated and i also added a heart shape to the customization option.(since i needed it for my project.) jitpack.io build is currently not working but maybe when i'll be bothered (and mostly figure out how to repair it since i ca'nt seem to figure out how to deploy the dependencies from gradle and jitpacks documentation also doesnt work for me) i will repair it. Also updated the sample lib to androidx and included the heart symbol in the selector radio group

To use React Native Hermes, you need to make a few changes to your project's configuration. Firstly, you must enable Hermes in your React Native project by modifying the android/app/build.gradle file. You need to replace the default jcenter() repository with maven { url 'https://jitpack.io' } and add the Hermes dependencies.

buildscript { ext { kotlin_version = '1.2.31' anko_version = '0.10.4' room_version = '1.0.0' support_version = '27.1.0' firebase_version = '12.0.0' gms_version = '12.0.0' } repositories { google() jcenter() maven { url 'https://dl.bintray.com/kotlin/kotlin-dev' } maven { url 'https://maven.fabric.io/public' } } dependencies { classpath 'com.android.tools.build:gradle:3.1.0' classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin\_version" }}allprojects { repositories { google() jcenter() mavenCentral() maven { url "https://jitpack.io" } maven { url 'https://dl.bintray.com/kotlin/kotlin-dev' } }} And this is my app's build.gradle file:

pluginManagement { repositories { gradlePluginPortal() google() mavenCentral() } } dependencyResolutionManagement { repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS) repositories { google() mavenCentral() maven ("https://jitpack.io") } } rootProject.name = "New Empty Compose App" include ("app")

repositories { //place it says ; should be used mavenCentral() maven { url = uri("https://jitpack.io") } }

Java -> Logback, Log4j2, JDK (Java Util Logging), Slf4j, e.t.c.

This is a GitHub link to my demo app. It’s simple Spring Boot web app used to debugging various stuff. There are many ways to configure JSON logging in Spring Boot. I decided to use Logback because it is easy to configure and one of the most widely used logging library in the Java Community. To enable JSON logging we need to add below dependencies.

Logback(https://logback.qos.ch/) is another non-commercial Java logging framework. It labels itself as a successor to the previously discussed Log4j framework.

> Then apache decides to put new people on log4j, do a backward incompatible v2 design that nevertheless is worse than slf4j. Why?

slf4j itself isn't a logging framework. It's a facade to logging frameworks.

Simple Logging Facade for Java ( https://www.slf4j.org )

It needs a logging framework behind it - log4j, log4j2, logback, commons, JUL.

The question is "why do log4j2?"

Logback went from the log4j1.x path ( https://logback.qos.ch )

Log4j2 has a lot of features that weren't present when the project started ( https://en.wikipedia.org/wiki/Log4j#Apache_Log4j_2 ).

There is a licensing difference between Logback (LGPL) and Log4jx (Apache Commons).

Also, I'd like you to pay attention to the log consumer. You see, when the E2E scenario fails, it's not always obvious why. Sometimes to understand the source of the problem you have to dig into containers' logs. Thankfully the log consumer allows us to forward a container's logs to any SLF4J logger instance. In this project, containers' logs are forwarded to regular text files (you can find the Logback configuration in the repository). Though it's much better to transfer logs to external logging facility (e.g. Kibana).

This shows that the MariaDB JDBC driver uses Logback as a logging framework. Although Logback is not affected by Log4Shell, it has a related vulnerability (of much lesser severity, no need to panic) fixed in version 1.2.8 and 1.3.0-alpha11. I checked the version used by the connector and found that it used 1.3.0-alpha10. Even though Logback is included as a test dependency in the MariaDB driver, I sent a pull request on GitHub to update it. I encourage you to do the same in any open-source project you find and that includes a vulnerable dependency.

Dependencing on the project, changing the logger might range from easy peasy to a multi-week task. I'm ready to bet that in many (most?) cases, it'd actually be quite easy, so let's explore how to do it, using Logback as the target (there aren't that many alternatives actually).

behold logback doing a bunch of JNDI fixes: https://github.com/qos-ch/logback/commit/c43bd30e1092b89bb91f5fb6a28310956b3bac61