[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=19758#comment-19758 ] 

John Patrick commented on SLF4J-420:
------------------------------------

I don't really mine what the JPMS module name is, as for the past 3 years I've been having to use the file based module name so that was/is slf4j.api.

But I would assume it's most logical name for the org.slf4j:slf4j-api artifact to be org.slf4j.api.

I'm restricted from building and releasing code that is still considered alpha/beta/RC. So I can't use your 15 month old 1.8.x beta or the 6 month old 2.0.x alpha.

I don't understand what the objection is to add the Automatic Module Name to the 1.7.x branch. If the maven artifacts are just minor or major version upgrades and it's using the same module name it means people can start using the correct module name and get the true JPMS benefits when 1.8.x and/or 2.0.x are finally released.

Yes some project use/depend on old versions, I'm trying to get them upgraded too. I've got forks of some projects I'm trying to get merged using the correct module names but I don't want to merge module-info.java files which contain filename-based automodules detected as it just causes issues once the project actually start using a module name.

For me log4j-over-slf4j was just more a comment as i noticed it, for testing and runtime I've not yet really cased about and just open as needed, trying to sort out the compile time first.

Just to confirm, once I found slf4j I switched over everything I could. I really like what it is, everything i write is slf4j with a log4j backend (because of ease of both MDC and the programmatic based configuration file reloading option).

Adding other Java 8 or newer features into slf4j I'm happy to wait until ready and full working as 1.7.x gives me everything i currently need apart form being able to do module builds. I'm aware you have issues as it doesn't produce a full module map but it's once less issue in the future and will be fixed once i get a java 11 version of slf4j.

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