Add JPMS support using Automatic-Module-Name

[mechite]

Understandably this project is unmaintained and pointless for a long time. However, many libraries, especially proprietary ones, still make use of commons-logging.

It is ideal if we can simply reserve the org.apache.commons.logging module name so that it is safe to publish these artifacts, and this artifact doesn't prevent migration of ancient projects to JPMS.

[bowbahdoe]

        <configuration>
          <archive combine.children="append">
            <manifestEntries>
              <Automatic-Module-Name>org.apache.commons.logging</Automatic-Module-Name>
            </manifestEntries>
          </archive>
        </configuration>

It seems like this is already done - is this configuration not enough/not functioning correctly?

(There isn't really a reason not to give a full module-info anyways)

[mechite]

It is not - I have currently a modified JAR deployed to my local repository with Automatic-Module-Name set in order to achieve this.

I do agree though - dmlloyd/module-info can be used to generate the file without dropping support for Java <8, or alternatively a java9 source directory created and module-info built seperately.

In any case, Automatic-Module-Name should be set and working as soon as possible in order to reserve the name.

[bowbahdoe]

There is also https://github.com/moditect/moditect, which i've used in PRs to other repos. Would maybe want to/have to set that up in commons-parent first though.

[garydgregory]

Moditect will be used for the next release, see the definition in commons-parent.

[mechite]

When is this release scheduled?

[garydgregory]

When is this release scheduled?

There is no schedule but it is on my to-do list.

[garydgregory]

Closing: module info file generated by parent POM.