[slf4j-dev] [JIRA] (SLF4J-420) Make a release with Automatic-Module-Name

[QOS.CH (JIRA)]

    [ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19757#comment-19757 ] 

Ceki Gülcü commented on SLF4J-420:
----------------------------------

{{\{quote}}}

{{why is log4j-over-slf4j just "log4j", because if you have an old dependency for log4j and need to use file name based modules, then that module will be called "log4j", should it not be "org.slf4j.log4j?}}

{{\{quote}}}{{}}

Your question contains the answer? As you put it, i{{f you have an old dependency for log4j and need to use file name based modules, then that module will be called "log4j".}}

 

{{\{quote}}}{{}}

{{Also as these maven modules for 1.x appear to match 2.x, then whey can't these names be used for a 1.7.27 release so those downstream projects that have been waiting for nearly 2 years can upgrade easily without have to do a major upgrade release...}}

{{\{quote}}}{{}}

It's quite late here and I don't understand. Can  you please give an example?

> Make a release with Automatic-Module-Name
> -----------------------------------------
>
>                 Key: SLF4J-420
>                 URL: https://jira.qos.ch/browse/SLF4J-420
>             Project: SLF4J
>          Issue Type: Task
>            Reporter: Gael Lalire
>            Assignee: Ceki Gülcü
>            Priority: Trivial
>             Fix For: 1.7.27
>
>
> You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta.



--
This message was sent by Atlassian JIRA
(v7.3.1#73012)