[
https://issues.apache.org/jira/browse/WICKET-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486309#comment-17486309
]
Thomas Kamps commented on WICKET-6955:
--------------------------------------
We restricted the slf4j verison as follows
{code}
api("org.slf4j:slf4j-api") {
version {
strictly("1.7.35")
}
because("We have no compatible log4j implementation for
slf4j-2.0.0-alpha5")
}
{code}
We need this constraint, because othwise the slf4j2 version does not find a
usable logger implementation and therefore no logs are printet out.
With it Gradle is not able to reolve a slf4j version that satisfies the
dependencies constraints.
> 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)
