Louis Jacomet comments

Results 109 comments of


                                            Louis Jacomet

Make build compatible with Gradle configuration cache

Currently the build does not accept the configuration cache because the license plugin used is not compatible.

Make build compatible with Gradle configuration cache

Closing as obsolete since the plugin code moved elsewhere.

Extra Slf4J provider: redshift-jdbc42

Replaced by: * gradlex-org/jvm-dependency-conflict-resolution#165

Make the plugin aware of `ch.qos.reload4j:reload4j`

Hi @erdi , Thank you for your interest in the plugin. A PR is most definitely welcome.

Make the plugin aware of `ch.qos.reload4j:reload4j`

Replaced by: * gradlex-org/jvm-dependency-conflict-resolution#162

Make plugin compatible with component metadata rules declared in settings.gradle

Thanks for that report and it is a good point. I'll have to think a bit about the best approach for this one.

Make plugin compatible with component metadata rules declared in settings.gradle

I am going to close this as obsolete. With the move to the [jvm-dependency-conflict-resolution plugin](https://github.com/gradlex-org/jvm-dependency-conflict-resolution/), rules defined in settings are an option.

Patch logback >= 1.3 to require slf4j >= 2.0, logback < 1.3 to require slf4j <= 1.7.x

Indeed, full support for [`slf4j` 2](https://github.com/ljacomet/logging-capabilities/issues/32) was never added. I still need to take a look at your PR.

`LOG4J_SLF4J_IMPL` vs. `LOG4J_SLF4J2_IMPL` for `enforceLog4J2()`

According to [the documentation](https://logging.apache.org/log4j/2.x/log4j-slf4j-impl.html), this depends on the version of `slf4j` in use. I need to check what can be done there and whether this decision can be made automatically...