jpackage-maven-plugin | JPackage Maven Plugin | Plugin library
kandi X-RAY | jpackage-maven-plugin Summary
kandi X-RAY | jpackage-maven-plugin Summary
JPackage Maven Plugin
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Build jpackage options .
- Executes the given command line
- Gets the JPackage from the installation directory .
- Validates the launcher configuration
- Escape arg .
- Gets the name .
- Checks if the current operating system is Linux .
- Determines whether a string is not empty .
- Determines if a string is empty
- Checks if the current operating system is a mac .
jpackage-maven-plugin Key Features
jpackage-maven-plugin Examples and Code Snippets
Community Discussions
Trending Discussions on jpackage-maven-plugin
QUESTION
I just started using jpackage and it is a really great tool. One single step takes a lot of work off my shoulders. The more surprised I am about something that looks hardcoded and cannot be customized?
JPackage automatically generates the launcher (lib/.desktop
file), and the deb package automatically installs it such that all users can launch the application. But as soon as it is launched, another icon pops up in unity. I expected that the existing icon is marked as running.
According to Ubuntu DEB installer makes all Java applications have the same icon we just need to ensure the .desktop file contains the correct StartupWMClass
. Using xprop I found out this value is based on the fully qualified class name responsible for the window - which makes absolute sense.
So how can I tell jpackage which StartupWMClass to set in the generated .desktop file?
Edit: To complement Bodo's comment I will show how I call jpackage. In fact I am not running a command line myself - instead I am using the maven plugin configured as:
...ANSWER
Answered 2022-Jan-20 at 23:05So finally I found a possibility to have the right packaging.
You need to override the JPackage internal template and provide your own .desktop file. This can be done by overriding JPackage resources.
It means you create a resource folder with the correct .desktop file inside, specify the resource folder on the JPackage command line and the correct package will be created.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install jpackage-maven-plugin
You can use jpackage-maven-plugin like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the jpackage-maven-plugin component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page