You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@johnzon.apache.org by "Samael Bate (Jira)" <ji...@apache.org> on 2023/06/10 10:40:00 UTC

[jira] [Created] (JOHNZON-398) Support JPMS fully via module-info.java rather than Automatic-Module-Name

Samael Bate created JOHNZON-398:
-----------------------------------

             Summary: Support JPMS fully via module-info.java rather than Automatic-Module-Name
                 Key: JOHNZON-398
                 URL: https://issues.apache.org/jira/browse/JOHNZON-398
             Project: Johnzon
          Issue Type: Improvement
          Components: Core, JAX-RS, JSON-B, Mapper, Websocket
            Reporter: Samael Bate


relates to: JOHNZON-305

 

When [https://github.com/apache/johnzon/pull/99] (see JOHNSON-305) was merged it was adding module names for packages using the _Automatic-Module-Name_ mechanism that can be set in the manifest. To fully support JPMS a project should configure which packages are required and exported by means of a _module-info.java_ file under {_}src/main/java{_}.

I've created & pushed a branch which does this while also configuring maven to not use the module path for test sources (a new feature in maven-compiler-plugin). This was the unit tests can still run as-is without needing to be concerned about split-packages (the alternative would be to change namespaces for all unit tests).

I believe that everything that needs to be exposed from the modules is available but a good review would be needed.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)