JavaPackager is a hybrid plugin for Maven and Gradle which provides an easy way to package Java applications in native Windows, Mac OS X or GNU/Linux executables, and generates installers for them. SNAPSHOT version is not released to Maven Central, so you have to install it manually. đź‘€ See JavaPackager changes and fixes. How to use this plugin. I got an Java application that does run under Java 1.8 without problems when I start its JAR directly. However on my Mac the JAR is wrapped within an app that demands me to install Java 1.6 - which I really do not want to do! So I'm searching the point within the app package where I could configure that my App shall use the installed Java 1.8.
Are you serious? Easy deployment is the primary thing to LIKE about Java, much more so than the actual language.In the Java world, your application dependencies are managed at the (gasp!) application level. You run Maven, Gradle, or whatever... and get a self-contained web archive (i.e. WAR file), with all of the application dependencies bundled. It's just a plain ZIP file, with a standard directory layout.
With a light app server such as Tomcat or Jetty, you literally just drop that file into a particular directory, and it's deployed! You just delete the file (and any contents that the app server unzipped), and it's undeployed!
- IzPack is a widely used tool for packaging applications on the Java™ platform. Easily make installers that work seamlessly on Microsoft Windows™, Linux™, Solaris™ and Mac OS X™. Keep your users happy right before they get their hands on your software for the first time. Read what our users say » Download IzPack ».
- Mac-package-name — Name of the application as it appears in the menu bar (defaults to the application name; must be less than 16 characters long and be suitable for displaying in the menu bar and the application Info window)-mac-package-signing-prefix — When signing the application bundle, the value prepended to all.
Pkg: Generates a.pkg package for OS X. Mac.appStore: Generates a package for the Mac App Store. Rpm: Generates an RPM package for Linux. Deb: Generates a Debian package for Linux.-nosign. If present, the bundle generated for self-contained applications is not signed by the bundler.
My Java App
If it's a console or GUI application rather than a web app, then you just create a JAR file in similar fashion. Maven has its 'shade' plugin, and all of the other build systems have similar counterparts... which will bundle up all of the application's dependencies into the JAR file as well. You then ship that monolithic JAR file anywhere, just as you would a '.exe' file. Assuming that you declared a main class when you built the JAR, you can execute it on any system by typing 'java -jar file_name.jar'... or by simply double-clicking it in a desktop environment.
Whenever I've dabbled with Python, Ruby, or NodeJS... I've been STUNNED to learn that they follow the ancient Perl convention, of managing application dependencies at the global interpreter level. If I want to write two applications with conflicting sets of dependencies, then I have use a tool such as 'virtualenv' (or its Ruby equivalent), to trick my environment into thinking that it's running in a completely different interpreter. NodeJS is somewhat more sane, in that 'npm' supports local and global dependencies... but you still have to ensure that you haven't installed a dependency in the wrong place, and that your target machine will have what you need in the correct place.
Newest App For Java
The current state of distribution and deployment for 'dynamic' languages is so insane, that people are actually excited about the idea of shipping an ENTIRE CHROOT JAIL as a deployment unit (i.e. Docker). People are using that in production environments, even though the Docker devs themselves tell you that it's not ready for that yet, because in half-baked form it's still better than the traditional options.
Java App For Mac
Java has many drawbacks, but distribution and deployment are NOT among them. Most of the people who upvoted this probably just reject Java as old and stuffy, and have not actually done significant work with it. If they had, then there might be at least one comment on this thread pointing out that Packr is a clone of Launch4j (http://launch4j.sourceforge.net)... which has been around for almost a decade now.