I would like to know whether anyone has used install4j to build an installer for a non java-based application? I'm looking to select a cross platform installer which has support to build java-based as well as non java-based applications. In the install4j official web site, it's introduced as cross platform installer for java-based applications. But I would like to know whether anyone has tried to build an installer using install4j for a non java-based application?
It's certainly possible, but keep in mind that the installer needs a JRE to run. You can bundle a JRE with the installer.
The Java-functionality around generating launchers will not be useful to you if you're not distributing a Java application, but most of the installer actions are not tied to Java launchers.
Related
Is there any ready-made installer, component, api or any combination, that would let a JavaFX application, or any JVM based client for that matter, automatically and securely check for a new version of itself, and get, install and re-launch the new version?
Although not ideal, is it doable at least with sbt?
in the Moment there is only a feature request for Java 9
Take a Look at this aproach which seems straight forward
AutoUpdate by Reportmill
Install4J is a a tool for creating installers for JVM applications, it provides for creation of auto-updates
https://www.ej-technologies.com/products/install4j/features.html
You can also build Install4J projects from SBT using the sbt-install4j plugin (disclaimer: I am the author of the plugin).
I have come to believe that the most practical (partial) solution is Java Web Start. Mature, documented, and comes along with the JRE and JDK. I wonder if anyone had experience with it for ScalaFX or JavaFX applications.
I am new in java and i have developed one simple application using netbeans7.2 and i am confused for how to create installer for my application to install it on users pc. I am listen about install4j and inno setup so please tell me which is better from both of these or any other way to create installer without using any setup creation software.
If you are talking about NetBeans Platform applications then NetBeans comes with its own installer, called NBI. You can have the IDE build installers for you. All in all: no need to use install4j or inno.
Is AIX support GWT app.
If no then do we have any other app like GWT which can run on AIX?
The programs generated by GWT are web applications (GWT makes it possible to develop the frontend, i.e. the user interface for a web application, in Java), so you can use a GWT app anywhere.
The developer tools for creating a GWT app are Eclipse, an Eclipse plugin, a Java SDK, and some browser add-ons for testing. I don't know if the add-ons for testing work on AIX, but everything else should. The developer tools are otherwise supported on Windows, Mac, and Linux.
I need to automate the building and deployment of (several) BPEL applications to a weblogic server.
I now do it using jDeveloper 11g, but I guess there should be some command line tools to do it. (I come from a Microsoft /.NET / Visual Studio background, and I can automate the deployment of my .NET applications using the command line and msbuild)
Does anyone know how to do that via the command line?
I don't have any experience with BPEL on Oracle WebLogic but according to this documentation a BPEL application is packaged as a standard EAR. I don't know exactly how your sources are structured under JDeveloper but you best option here to automate the packaging and the deployment of this EAR is IMO to use Ant (or Maven but if all this is totally new for you I would recommend using Ant).
Maybe this tutorial can help you to get started for the packaging part (basically, how to use the ear task). And for the deployment, I suggest to use the wldeploy Ant task (which wraps the weblogic.Deployer utility). I've mentioned them in this recent answer.
Also have a look at this question, it seems that JDeveloper might have some support to achieve this task (but I have zero knowledge of it so I can't provide any guidance, JDeveloper is not really widely used).
I assume you are using Oracle SOA Suite 11g? If so, have a look at Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite, particularly the section 38.7 Deploying SOA Composite Applications and the subsection 38.7.5 Managing SOA Composite Applications with Scripts.
You may also find useful advice in the Oracle BPEL forums.
I've recently started learning SWT (on class #4, to be precise) due to business requirements, and previously I had been developing with Swing for 2 years.
We deployed Swing applications as jars with resource dependencies. In SWT, what are the deployable forms and equivalents?
I have questions but since my training is online, I'm on a course-ware and there is no instructor, except StackOverflow:
Can SWT apps be deployed as independent EXE's? And what's with the "Eclipse EXE" thing people talk about? Does it mean that all SWT outputs will be Eclipse based EXEs? Or can they be completely independent EXEs?
If the answer to 1 is yes, how does the compiler produce native win32 executable code? This is one area where I'm thoroughly confused. Typically, a deployable jar is fed to the VM which reads the manifest and does its stuff, but an EXE as output? What's really behind the scenes?
How are external resource bundles managed? At the time of deployment?
Internationalization support?
Thanks.
Deploying an SWT application is exactly like deploying a Swing app, with the addition of several jars and a native library. You must currently be using some tool to make exe files for your Swing app; that tool may or may not be competent to also package up a native code library. It is unlikely that the tool is creating 'native win32 executable code'. Rather, it is packaging up Java class files along with the JRE and a stub Windows PE file.
SWT is developed as part of Eclipse. Eclipse has the Rich Client Platform, or RCP. If you build your Java application as an RCP application, you can use the Eclipse tools to generate an executable package for Windows (or anywhere else). It is not a single executable, it's a directory with an executable in it. However, you don't have to use Eclipse to use SWT.
An RCP application has to use much more than just SWT. It has to be constructed as a set of OSGi bundles that depend on the core Eclipse platform. Once you have such a thing running inside Eclipse, there is a wizard in Eclipse that will create a Windows 'executable' (a directory containing your code in JAR file(s), a lot of Eclipse code in JAR files, the JRE, and a PE .exe stub). You can automate that process from ant, though I've never done it myself. You will need to do book-length reading to get up to speed on all of this, I fear.
There no difference between SWT and Swing in terms of resources and internationalization. Other Eclipse-related libraries include an I18N discipline, but not the core SWT. You just use locales and property files as in any other Java application.
SWT is not Eclipse-based, but the Eclipse UI is SWT-based. Eclipse uses the SWT library for its drawing. It is used a GUI library from the Eclipse consortium, available for many systems. If you want to deploy your normal Java Application with an SWT GUI you just add the corresponding libs and .dll's or .so's. Therefore, everything you can do (deployment) with Java respectively speaking Swing, can be done with SWT, if you provide the according libraries. There are tools and ways to compile everything into .exe's but that is not necessarily needed.
I do not really get the Eclipse EXE thing you are talking about, but eclipse just provides a starter exe, which is basically just a wrapper. Otherwise, some people refer to Eclipse RCP als Eclipse EXE but this is not correct. You CAN use the Eclipse RCP to base your App and this would use SWT as UI library. But you can use SWT all by yourself just as library without the Eclipse trail.
I hope this helps.
You can use a java to EXE wrapper like this one http://jsmooth.sourceforge.net/.
Hope it helps.
Basically you need to get your project running with the conventional java -jar command.
Then create an exe bootstrap program that runs the command when you double click it.
Extra things can be done like checking JVM versions inside the exe program.