[
https://issues.apache.org/jira/browse/LOGGING-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814827#comment-17814827
]
Samael Bate commented on LOGGING-187:
-------------------------------------
The title was correct at the time as I wanted the changes that were merged at
the time. Now {{commons-logging:commons-logging:1.3.0}} is available so this
ticket could be marked as done.
The reason for mentioning a possible v2 was in regards to what should be done
after 1.3.0 is published. Dropping Avalon & Lumberjack and replacing log4j 1
with log4j 2 could be done as either a 1.x or a 2.x but I feel it's worth going
fully into current day and making these changes as a v2 with other changes that
can break backwards compatibility for some users, such as Java 11 minimum.
After all, 1.x releases could still be done for Java 8 users.
> release current state of master as 1.3
> --------------------------------------
>
> Key: LOGGING-187
> URL: https://issues.apache.org/jira/browse/LOGGING-187
> Project: Commons Logging
> Issue Type: Task
> Reporter: Samael Bate
> Priority: Major
>
> master branch appears to be in a good state. Please can someone within Apache
> tag/publish a new release so that the following changes can be made as a v2:
> * Remove Avalon & Lumberjack loggers
> (https://issues.apache.org/jira/browse/LOGGING-173)
> * Replace log4j 1 with log4j 2
> (https://issues.apache.org/jira/browse/LOGGING-180,
> https://issues.apache.org/jira/browse/LOGGING-181)
> * Change _GroupId_ of maven artifact to *org.apache.commons* like other
> Apache Commons libs.
> * Potentially bump the minimum support JDK (v11 will be needed for recent
> logback)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
