If a class is referenced by a Main-Class attribute in a JAR manifest, for instance, DashO can update the manifest to use the updated name. However, in some cases they can be safely renamed. Generally, entry points should not be renamed because they are presumably accessed from outside the application. If you like, you can allow classes, methods, and/or fields on the Entry Points - Methods and Fields page to be renamed. These methods and fields will be excluded from both removal and renaming by default, and DashO will analyze the methods specified as entry points to determine which classes and members are unused. You can specify methods and classes that you would like to be entry points on the Entry Points - Methods and Fields page of the DashO GUI. If DashO fails to find any Entry Points in this manner, then it will treat all inputs as Library Entry Points, excluding all public and protected members of public classes from renaming and removal. If there are no Entry Points defined in your DashO configuration, then DashO will attempt to detect Entry Points by analyzing the manifests of all input jars (looking for, e.g., Main-Class headers), if any are present.ĭashO will also look for public static void main(String) methods.
0 Comments
Leave a Reply. |