[
https://issues.apache.org/jira/browse/MNG-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708774#comment-17708774
]
Michael Osipov edited comment on MNG-7670 at 4/5/23 9:31 AM:
-------------------------------------------------------------
> Michael Osipov I was under the impression that by maintaining two versions,
> logback was providing a service above and beyond. I should add that
> JMPS/Jigsaw compliance is already proving to be very difficult, doing so for
> both javax.* and jakarta.* seems quite beyond our means.
I know that this is much more than many would ask, thank you for that! I am
still convinced from my superficial view that it could have been simpler for
*you* or QOS as as maintainer.
Looking at https://github.com/qos-ch/logback/search?l=Java&p=2&q=jakarta I
don't think that they necessarily need to be in core. They could have been in
logback-javax-servlet/logback-jakarta-servlet and logback-javax-smtp
(mail)/logback-jakarta-smtp (mail). Remember: LOGBACK-1410, LOGBACK-1665,
LOGBACK-1699
Note: I am note complaining, I am looking at this from a maintainer's
perspective and the burdens which come with it.
was (Author: michael-o):
> Michael Osipov I was under the impression that by maintaining two versions,
> logback was providing a service above and beyond. I should add that
> JMPS/Jigsaw compliance is already proving to be very difficult, doing so for
> both javax.* and jakarta.* seems quite beyond our means.
I know that this is much more than many would ask, thank you for that! I am
still convinced from my superficial view that it could have been simpler for
*you* or QOS as as maintainer.
Looking at https://github.com/qos-ch/logback/search?l=Java&p=2&q=jakarta I
don't think that they necessarily need to be in core. They could have been in
logback-javax-servlet/logback-jakarta-servlet and logback-javax-smtp
(mail)/logback-jakarta-smtp (mail). Remember: LOGBACK-1410
Note: I am note complaining, I am looking at this from a maintainer's
perspective and the burdens which come with it.
> Upgrade misc dependencies
> -------------------------
>
> Key: MNG-7670
> URL: https://issues.apache.org/jira/browse/MNG-7670
> Project: Maven
> Issue Type: Dependency upgrade
> Components: Dependencies
> Reporter: Sylwester Lachiewicz
> Priority: Minor
> Fix For: 3.9.2
>
>
> [INFO] The following dependencies in Dependency Management have newer
> versions:
> [INFO] com.google.guava:guava .......................... 30.1-jre ->
> 31.1-jre
> [INFO] org.apache.commons:commons-lang3 ..................... 3.8.1 ->
> 3.12.0
> [INFO] org.codehaus.plexus:plexus-classworlds ................ 2.6.0 ->
> 2.7.0
> [INFO] org.codehaus.plexus:plexus-component-annotations ...... 2.1.0 ->
> 2.1.1
> [INFO] org.codehaus.plexus:plexus-utils ...................... 3.4.2 ->
> 3.5.0
> [INFO] org.hamcrest:hamcrest-core ................................ 1.3 ->
> 2.2
> [INFO] org.hamcrest:hamcrest-library ............................. 1.3 ->
> 2.2
> [INFO] org.mockito:mockito-core ............................ 2.21.0 ->
> 4.11.0
> [INFO] org.powermock:powermock-reflect ....................... 1.7.4 ->
> 2.0.9
> [INFO] org.xmlunit:xmlunit-core .............................. 2.2.1 ->
> 2.9.1
> [INFO] org.xmlunit:xmlunit-matchers .......................... 2.2.1 ->
> 2.9.1
> Logback 1.3.x depends on SLF4J 2.x, Logback 1.4.x requires Java 11
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
