[
https://issues.apache.org/jira/browse/WICKET-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495959#comment-17495959
]
Thomas Kamps commented on WICKET-6955:
--------------------------------------
We can start and get logs with the enfored 1.7.35 version. but for the tests
Gradle is not able to resolve the slf4j-api dependency. We did not figure out
why there is a problem and if it our fault or not.
Using Wicket 9.4.0 everyting will build verything just fine. And since Wicket
9.4.0 uses slf4j 1.7, we assume that downgrading wicket to slf4j 1.7 will
resolve our problems. Also there is currently no log4j implementation for slf4j
2.0, wich forces us and other projects to manually downgrade slf4j to 1.7, if
they want to use log4j.
> Wicket uses unstable slf4j version
> ----------------------------------
>
> Key: WICKET-6955
> URL: https://issues.apache.org/jira/browse/WICKET-6955
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 9.5.0, 9.6.0, 9.7.0
> Reporter: Thomas Kamps
> Priority: Major
>
> Since Wicket 9.5.0 the dependency of slf4j has changed from 1.7.25 to
> 2.0.0-alpha2 or some later alpha versions.
> This change keeps us from upgrading to those versions, since there is
> currently no compatible Log4j implementation for slf4j 2.0.0-alpha (Which i
> can understand, because it is an alpha version, which can change its api
> rapidly).
> We tried to enforce using an 1.7 version, but that did not work because of
> some other libs that use slf4j in a 1.7 version.
>
> So please change the used the slf4j back to an relased 1.7 version.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
