[slf4j-dev] [JIRA] Updates for SLF4J-592: Mechanism for indicating provider to use for unit tests.

[slf4j developers list]

SLF4J / SLF4J-592 [Open]
Mechanism for indicating provider to use for unit tests.

==============================

Here's what changed in this issue in the last few minutes.


There is 1 comment.


View or comment on issue using this link
https://jira.qos.ch/browse/SLF4J-592

==============================
 1 comment
------------------------------

Garret Wilson on 22/Jun/23 17:20

{quote}If we are taking the route of system properties, we could simply let the developer tell us the preferred provider.{quote}

Ceki this is an exciting idea. (I guess brainstorming works!)

Before walking through the pros and cons of that approach, I decided to test it. It works fine with the Maven Surefire Plugin (e.g. {{mvn test}} on the command line). Unfortunately it doesn't work in Eclipse, because it turns out that the Eclipse IDE test subsystem is not connected to m2e at all; see my [comment|https://github.com/eclipse-m2e/m2e-core/issues/174#issuecomment-1602822473] at [m2e Issue #174|https://github.com/eclipse-m2e/m2e-core/issues/174]. Using this in an IDE was one of the main motivations of this request.

This holds a lot of promise, but I'm going to pause and think more about the ecosystem for a bit.


==============================
 This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)