-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
None
-
None
Summary
-------
In order to help migrating existing code to the new module system it would be good to have a tool that helps analyse existing code for split packages within the own source code.
This is at the moment one of the big problems after having used JDK internal classes as they can be found using the jdeps tool.
Goals
-----
Provide a simple tool like jdeps that analyzes existing compiled code and provides summary about split packages among the analyzed files.
Non-Goals
---------
It is not a goal, to refactor any existing code or even autoresolve split packages.
Motivation
----------
It should help to be prepare own code in order to move faster to the new module system.
Description
-----------
The usage should be in such a way, that a combination of .jar files or class folders can be specified, that are being considered as different modules. Those should be scanned and a simple overview of split packages and their source library/class folder.
Additionally it may be a good idea to list the total amount of classes in the respective libary/class folder. This could be further grouped in the respective access level.
-------
In order to help migrating existing code to the new module system it would be good to have a tool that helps analyse existing code for split packages within the own source code.
This is at the moment one of the big problems after having used JDK internal classes as they can be found using the jdeps tool.
Goals
-----
Provide a simple tool like jdeps that analyzes existing compiled code and provides summary about split packages among the analyzed files.
Non-Goals
---------
It is not a goal, to refactor any existing code or even autoresolve split packages.
Motivation
----------
It should help to be prepare own code in order to move faster to the new module system.
Description
-----------
The usage should be in such a way, that a combination of .jar files or class folders can be specified, that are being considered as different modules. Those should be scanned and a simple overview of split packages and their source library/class folder.
Additionally it may be a good idea to list the total amount of classes in the respective libary/class folder. This could be further grouped in the respective access level.
