For example, on Windows users expect to be able to double-click on a package to install their software, and then use the control panel to remove the software on macOS, users expect to be able to double-click on a DMG file and drag their application to the Application folder. This allows Java applications to be distributed, installed, and uninstalled in a manner that is familiar to users. It is not sufficient for the application developer to deliver a simple JAR file they must deliver an installable package suitable for the native platform. Many Java applications need to be installed on native platforms in a first-class way, rather than simply being placed on the class path or the module path. There is no native splash screen support. There will be no aggregation of individual license files. There is no special support for legal files beyond what is already provided in JMOD files. The packaging tool will depend upon platform-specific tools. For example, in order to create Windows packages one must run the tool on Windows. There is no support for cross compilation. ![]() There is no GUI for the tool a command-line interface (CLI) is sufficient.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |