gradle-launch4j | A gradle-plugin to create windows executables with launch4j | Plugin library

 by   TheBoegl Groovy Version: v2.5.4 License: Apache-2.0

kandi X-RAY | gradle-launch4j Summary

kandi X-RAY | gradle-launch4j Summary

gradle-launch4j is a Groovy library typically used in Plugin, Gradle applications. gradle-launch4j has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The gradle-launch4j plugin uses launch4j 3.14 to create windows .exe files for java applications. This plugin is compatible with the Gradle versions 2 and later. Since version 2.5 this plugin requires *Java 8, as launch4j in version 3.14 requires that as well. If you are still forced to work with Java 6, use the latest version 2.4.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              gradle-launch4j has a low active ecosystem.
              It has 266 star(s) with 44 fork(s). There are 10 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              There are 6 open issues and 88 have been closed. On average issues are closed in 270 days. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of gradle-launch4j is v2.5.4

            kandi-Quality Quality

              gradle-launch4j has 0 bugs and 0 code smells.

            kandi-Security Security

              gradle-launch4j has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              gradle-launch4j code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              gradle-launch4j is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              gradle-launch4j releases are not available. You will need to build from source code and install.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-launch4j
            Get all kandi verified functions for this library.

            gradle-launch4j Key Features

            No Key Features are available at this moment for gradle-launch4j.

            gradle-launch4j Examples and Code Snippets

            No Code Snippets are available at this moment for gradle-launch4j.

            Community Discussions

            QUESTION

            Gradle Launch4J EXE not trusted by Windows 10
            Asked 2019-Dec-10 at 09:39

            Please note: I have created this GitHub project right here that can be used to perfectly reproduce the problem I'm seeing.

            Java 8 here attempting to use Launch4J via the gradle-launch4j Gradle plugin to build a Windows native EXE application. I am doing the development of a Java Swing app on my Mac but the app must run as a Windows EXE on Windows 10. I am also using ShadowJar to build my self-contained "fat jar".

            I can build my (Swing) app's fat jar and then run it on my Mac via java -jar build/lib/myapp.jar. It starts and runs no problem.

            Here is my Gradle config for Launch4J:

            ...

            ANSWER

            Answered 2019-Dec-06 at 07:20

            Your first question is more like a Windows question. When you unzip an application from a zip file, Windows will naturally mark it as unsafe, in fact if you check the application properties tab, you will see a checkbox where you can remove that unsafe attribute. It's same as running chmod+x for an executable script in Linux.

            For the second part, I assume you are using the gradle plugin for Launch4j, there are two main ways to configure Launch4j assuming your project folder is structured commonly with the jre library in the same folder containing your executable folder.

            1. By specifying the path only like

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

            QUESTION

            Package java desktop app (gradle)
            Asked 2017-Nov-05 at 13:37

            According to this oracle docs there is a conventional java app packaging along with runtime JRE. (Self-Contained Application Packaging)

            I know that there is this thing (Launch4j gradle plugin) but I'd prefer to have a bat/sh executables along in the package.

            Going through gradle docs and googling I can not seem to find is there is a way to teach gradle to package desktop app with JRE. Is there?

            ...

            ANSWER

            Answered 2017-Nov-05 at 13:37

            QUESTION

            Sequencing dependencies of multiple Gradle plugin tasks
            Asked 2017-Mar-15 at 10:18

            Please note: Although I specifically mention two Gradle plugins here, this is 100% a question about understanding task dependencies in Gradle, and does not require any knowledge of the individual plugins (I think)!

            I have a project that will use two Gradle plugins:

            • The Gradle Shadow plugin, which will produce a self-contained "fat jar" (basically a large jar with all my classes plus the classes of all my transitive dependencies, which then allows me to just run java -jar myapp.jar without having to manage the jar's external classpath, etc.). This will produce a fat jar at build/libs/myapp.jar; and
            • The Gradle Launch4J plugin, which uses Launch4J under the hood to convert a jar into a native executable (EXE, etc.). Obviously the fat jar has to be created prior to the Launch4J tasks run, otherwise they'll have nothing to wrap inside of an EXE!

            Here's my build.gradle:

            ...

            ANSWER

            Answered 2017-Mar-15 at 10:18

            Once you write

            createAllExecutables.dependsOn shadowJar

            you'll define the dependency between createAllExecutables task and shadowJar, which means every time Gradle decide to invoke createAllExecutables (e.g. because you pass that to the command line, or other task will depend on it) shadowJar will also be added to the task graph. So in that case when you invoke gradle createAllExecutables the shadowJar will be also executed.

            But you can also write

            createAllExecutables.mustRunAfter shadowJar

            In that case, you won't introduce any dependency relation between tasks, but you will instrument Gradle about anticipated order for those two tasks. In that case, once you invoke gradle createAllExecutables the shadowJar won't be executed.

            I think the dependsOn relation is more applicable in your case, since in order to create executables you need to have fat jar already, so it's a depend on relation, not must run after.

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

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

            Vulnerabilities

            No vulnerabilities reported

            Install gradle-launch4j

            You can download it from GitHub.

            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:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/TheBoegl/gradle-launch4j.git

          • CLI

            gh repo clone TheBoegl/gradle-launch4j

          • sshUrl

            git@github.com:TheBoegl/gradle-launch4j.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link