[ 
https://issues.apache.org/jira/browse/LOGGING-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809659#comment-17809659
 ] 

Elliotte Rusty Harold commented on LOGGING-187:
-----------------------------------------------

If we change the group ID to org.apache.commons then we should also change the 
package names. Otherwise we're opening a barrel full of dependency conflicts 
and user pain in Java 9+ for the next several years. 

> 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)

Reply via email to