- This topic has 5 replies, 3 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
I’d like to see a feature for standalone Java apps which is similar to your “smart deployment” in webapps – the ability to create a
jar file which includes everything not part of the JDK which is required to run an application. In Windows this would mean simply double clicking on the jar file. The Matisse Swing editor looks good, but without the fat jar function you can’t build a standalone clickable jar no matter how simple the program because it requires swing-layout-1.0.jar file.There are licensing issues here that I think become problomatic. I would point out that if you edit your MANIFEST.MF file correctly and specify the location of your swing-layout.jar you can double click the JAR and run it.
I will say that the feature request is interesting and I can certainly file it, it might have already been on folk’s minds.
I didn’t mean to imply that you should bundle the fat jar plugin that’s out there into MyEclipse – that
might cause some issues. Rather I’d like to point out that the same kind of thing you do for
war files and smart deployment would be very useful for standalone jar exports. I would think
that you’d have no more licensing issues with jar files than you would with the war files you already produce. As for redistribution/licensing issues with swing-layout-1.0.jar itself, that file is just an example
of where this would be useful and those types issues aren’t really the concern of the tool anyway, just the humans who use it.I would like to extend this and make it so that stand-alone SWT or RCP apps can be exported as exe files (or dmg or whatever).
I want native installers! Oh, and they should detect the current JVM on the users computer and point/download the correct one, if needed…
It seems there is already a plugin that has this functionality… I am evaluating it right now:
