Later would-be-nices, not for this desktop app, but ability to use it to package background service-type apps, as a service for windows, using launchd for osx, and systemd for linux.
macOS:
Create additional two packages when building a package with services. One will install launched-specific .plist files in /Library/LaunchDaemons folder. Another one will install /Library/Application Support/<app_name>/uninsatll.command shell script with commands removing app's services from the system.
Package IDs for these two packages will be <app_pkg_id>.services and <app_pkg_id>.support accordingly.
If the app's package ID is "com.dukecorp", then ID for additional packages will be "com.dukecorp.services" and "com.dukecorp.support".
macOS:
Create additional two packages when building a package with services. One will install launched-specific .plist files in /Library/LaunchDaemons folder. Another one will install /Library/Application Support/<app_name>/uninsatll.command shell script with commands removing app's services from the system.
Package IDs for these two packages will be <app_pkg_id>.services and <app_pkg_id>.support accordingly.
If the app's package ID is "com.dukecorp", then ID for additional packages will be "com.dukecorp.services" and "com.dukecorp.support".
- csr for
-
JDK-8275062 Allow jpackage create installers for services
- Closed
- duplicates
-
JDK-8208304 [packager] Service Bundler Support
- Closed
- relates to
-
JDK-8285736 JDK-8236128 causes validate-source failures
- Closed
-
JDK-8230668 ☂ Windows packaging suggestions
- Closed
-
JDK-8333116 test/jdk/tools/jpackage/share/ServiceTest.java test fails
- Resolved
-
JDK-8285616 [macos] Incorrect path for launcher-as-service.txt in .cfg file
- Closed
(1 relates to, 2 links to)