jpackage-maven-plugin | JPackage Maven Plugin | Plugin library

by petr-panteleyev Java Version: 1.6.3 License: BSD-2-Clause

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | jpackage-maven-plugin Summary

jpackage-maven-plugin is a Java library typically used in Plugin, Maven applications. jpackage-maven-plugin has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

JPackage Maven Plugin

Support

Quality

Security

License

Reuse

Support

jpackage-maven-plugin has a low active ecosystem.

It has 25 star(s) with 7 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 2 have been closed. On average issues are closed in 3 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jpackage-maven-plugin is 1.6.3

Quality

jpackage-maven-plugin has 0 bugs and 0 code smells.

Security

jpackage-maven-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jpackage-maven-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jpackage-maven-plugin is licensed under the BSD-2-Clause License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jpackage-maven-plugin releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

It has 4504 lines of code, 32 functions and 25 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed jpackage-maven-plugin and discovered the below as its top functions. This is intended to give you an instant insight into jpackage-maven-plugin implemented functionality, and help decide if they suit your requirements.

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 .

Get all kandi verified functions for this library.

jpackage-maven-plugin Key Features

No Key Features are available at this moment for jpackage-maven-plugin.

jpackage-maven-plugin Examples and Code Snippets

No Code Snippets are available at this moment for jpackage-maven-plugin.

Community Discussions

Trending Discussions on jpackage-maven-plugin

jpackage linux creates insufficient desktop file

QUESTION

jpackage linux creates insufficient desktop file

Asked 2022-Jan-20 at 23:05

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:05

So 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.

Source https://stackoverflow.com/questions/70420618

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jpackage-maven-plugin

You can download it from GitHub, Maven.
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

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: