[
https://issues.apache.org/jira/browse/WICKET-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495225#comment-17495225
]
Daniel Stoch commented on WICKET-6955:
--------------------------------------
Is there any reason that Wicket uses slf4j 2.x, does it use some specific 2.x
API (fluent API)?
If not then (according to Slf4j FAQ) Wicket >= 9.5 probably can run without any
problems with previous version of slf4j 1.7.x or am I wrong?
Currently it is not possible using OSGi, because in Import-Package min version
is 2.0:
{noformat}
org.slf4j;version="[2.0,3)"
{noformat}
So maybe this can be changed to:
{noformat}
org.slf4j;version="[1.7,3)"
{noformat}
?
> 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)
