Wolfgang Knauf created AXIS2-6040:
-------------------------------------
Summary: Define Automatic-Module-Name for Java9 module system
compatibility
Key: AXIS2-6040
URL: https://issues.apache.org/jira/browse/AXIS2-6040
Project: Axis2
Issue Type: Improvement
Components: kernel
Affects Versions: 1.8.2
Reporter: Wolfgang Knauf
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]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
