Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-6040

Define Automatic-Module-Name for Java9 module system compatibility

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 1.8.2
    • 1.8.3
    • kernel
    • None

    Description

      After Java9 module system compatibility was fixed through https://issues.apache.org/jira/browse/AXIS2-4311, I used Eclipse to create a "module-info.java" to my small sample project.

      This is the resulting module-info.java file:

      module myprojectname
      {{{}}
        exports my.own.project.package;
        requires axiom.api;
        requires axis2.adb;
        requires axis2.kernel;
        requires commons.logging;
        requires jakarta.activation;
        requires java.rmi;
        requires java.xml;
      }

       

      This results in four eclipse warnings:

      Name of automatic module 'axiom.api' is unstable, it is derived from the module's file name.
      Name of automatic module 'axis2.adb' is unstable, it is derived from the module's file name.
      Name of automatic module 'axis2.kernel' is unstable, it is derived from the module's file name.
      Name of automatic module 'commons.logging' is unstable, it is derived from the module's file name.

      As far as I understand it, it would be sufficient to add a "Automatic-Module-Name" entry to Manifest.mf for the Axis2 jars- see e.g. https://github.com/ReactiveX/RxJava/issues/5618

       

       

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            wknauf Wolfgang Knauf

            Dates

              Created:
              Updated:

              Slack

                Issue deployment