-
Below pages quite clearly state that logback 1.5.x is for Jakarta EE (jakarta.* namespace) and 1.3.x is for Java EE (javax.* namespace):
However, I noticed that 1.5.x runs just fine with an application which is using javax namespace. This application uses embedded jetty jetty-ee8-webapp 12.0.16 (so javax with servlet api 4). Logback dependencies are logback-core and logback-classic with 1.5.16 version and logback-access-jetty12 with 2.0.6. To my surprise, the server starts up just fine with these dependencies and logging works just as expected: both access logs and other logging works just fine. I have not seen any issues. So just wondering what are the features which will not work with this setup when using logback 1.5.x in javax namespace? We use pretty basic stuff from logback, so basically just basic logging and access logging. I would definitely want to keep using 1.5.x version, however, a bit concerned about that it is not really recommended in the docs, so wondering impacts of this one. I could not use latest 1.3.x release in this application since the jetty 12 (jetty-ee8-webapp) did not seem to work with older logback access dependency, so have to use the latest logback-access-jetty12 which requires then logback 1.5.x. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
As long as you are not logging via a servlet or emailer, then it will work fine. You can easily see this by this search https://github.com/search?q=repo%3Aqos-ch%2Flogback%20%22import%20jakarta%22&type=code |
Beta Was this translation helpful? Give feedback.
As long as you are not logging via a servlet or emailer, then it will work fine. You can easily see this by this search https://github.com/search?q=repo%3Aqos-ch%2Flogback%20%22import%20jakarta%22&type=code