Install4j deletes jre\bin folder during installation - install4j

I am using Install4j 6.1.1 to create a new installer that must be smart enough to support 3 installation scenarios:
Create a new installation
Upgrade an existing installation
Upgrade an existing installation that was created using an InstallAnywhere installer
Scenarios 1 and 2 function correctly. With scenario 3 there is a problem with installing a new jre.
If my installer finds an old non-Install4j instance, it invokes the previous version's uninstaller before proceeding with a new install. This seems to work just fine. However, the new bundled JRE is not being installed properly. The Install Files action copies the JRE to the install folder, and then the deletes the bin folder. This results in a corrupted installation that will not execute. I can see this happen- if I open the JRE subfolder during install I can see the jre's lib and bin folders get created and then watch the bin folder get deleted. The jre\lib folder remains. There does not seem to be anything in the installation log to explain what's happening.
Any idea what would cause a bundled JRE to partially install?

Related

Bundled JRE error with install4j installer packaged as msix

We create an installer with install4j that bundles the JRE. We then use the MSIX Packaging Tool to create a .msix installer, to publish on the Microsoft App Store.
When we install the .msix package for testing and try to run the application, we get the following error:
"The JVM found at .\jre is damaged. Please reinstall or define EXE4J_JAVA_HOME to point to an installed 64-bit JDK or JRE"
Note that the JRE is bundled with the installer, and it is actually installed in a folder called "jre" under the installation folder.
When we install from the .exe installer, everything works fine, this problem only happens after we create a .msix installer with the MSIX Packaging Tool. We've checked all the installed files and everything looks fine, but the launcher will not run.
Has anybody seen this problem? And is there a solution or workaround?

Apache Netbeans 11.0 not appearing in Add/Remove Programs Windows 10

I installed Apache Netbeans a couple weeks ago, decided I didn't like it, and am attempting to uninstall it. However, it is not showing up in my Add/Remove Programs on Windows 10, nor can I find an Uninstall exe file in the files of NetBeans. Any help or advice would be appreciated.
You must have installed Apache NetBeans 11.0 by downloading a zip file named incubating-netbeans-11.0-bin.zip, then unzipping it to an installation directory, because that is the only approach that is offered. From the Apache NetBeans web site:
Apache NetBeans 11.0 is available for download from your closest
Apache mirror. For this release no official installers are provided,
please just download the binaries and unzip them.
This explains why you cannot uninstall NetBeans 11.0 from the Control Panel in Windows 10: you did not install it using an installer, you just unzipped a file.
So to uninstall NetBeans 11.0 on Windows 10 all you need to do is this:
Close NetBeans.
Delete the NetBeans installation directory.
Delete the downloaded zip file (if you had kept it).
However, there are a couple of additional optional steps that will free up (a lot of) disk space, and are definitely worth doing:
Before removing/uninstalling NetBeans, open it one last time.
Open the Help > About screen. You will see a couple of entries named User directory and Cache directory. They contain (a lot of) files related to the configuration of NetBeans, and they can and should be deleted as well:
Note the names of those two directories, and then close NetBeans.
Delete those two directories, and then delete the NetBeans installation directory and the downloaded zip file (if necessary).

The Eclipse executable launcher was unable to locate its companion shared library on shared drive after silently updating Equinox launcher

I have Eclipse installed on a removable drive that I take between my desktop and laptop. I have an old installation (Mars) that I installed ages ago by unzipping files. I have a newer installation (Neon) that I installed using the new Eclipse installer.
After upgrading both my computers to Windows 10 Anniversary Edition, both Eclipse installations continue to work when the drive is connected to the desktop machine. When I connect the drive to the laptop, however, the new Eclipse installation (Neon---the one installed using the installer) will not start and says:
The Eclipse executable launcher was unable to locate its companion shared library.
However the old installation (Mars---the one installed from unzipping an archive) still runs just fine.
What is the problem with the Neon installation on the laptop and how do I fix it?
Update: I looked in the eclipse.ini file, and there is a --launcher.library reference to a C:/Users/user/.p2/pool/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.400.v20160518-1444. The laptop (which is failing) has only org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417. But the desktop (where it is working) has both org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417 and org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.400.v20160518-1444.
So maybe somehow Eclipse updated its Equinox Launcher when the drive was attached to the desktop. Then when I attached the drive to the laptop, it referenced the updated launcher plugin, but the laptop didn't have the updated launcher.
This is a fine kettle of fish. I had no idea Eclipse was installing things in the user directory, outside the Eclipse installation directory. I guess that's one of the drawbacks of this newfangled launcher: it's not possible to use Eclipse on a shared drive.
How can I get Eclipse to install the launcher on the shared drive rather than in the system user home directory? Can I avoid this altogether if I install directly from zip files? How did Eclipse update this launcher in the first place without my knowing about it?
Update: Now I see that Eclipse also installed a org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar in the local plugins directory (that is, relative to the executable on the drive). Why is Eclipse putting some things on the removable drive relative to the executable (as they should be), and other things in the system user directory (where I don't want them)? This is a mess. So much for having a self-contained Eclipse installation like I did for over a decade.
By default, Eclipse installer does use a shared "bundle pool" so that if you have multiple different Eclipse instances running, the various plugins they're using are only downloaded once. This usually saves network bandwidth and disk space.
However, this bundle pool may probably be unable to work properly if the installation and bundle pool are on different drive (Especially if one of them is shared by multiple machines). You can report this limitation to http://bugs.eclipse.org .
As a workaround, for such custom installations, I would recommend that you skip the Eclipse installer, and get good old packages that will work just like Mars, everything in their own directory: https://www.eclipse.org/downloads/eclipse-packages/

How can I completely uninstall eclipse on Ubuntu14.04

I install eclipse on Ubuntu14.04 for hadoop program, and there're always some troubles with the hadoop plugin. So I install and uninstall eclipse for two times. But I'm not sure whether it was completely removed.
The last time I install eclipse from the Ubuntu software center. I click the uninstall button in the software center and then delete the folder /usr/lib/eclipse(where eclipse installed). But I also find 'eclipse.ini' in /etc. Can I delete the file?
In order to completely remove eclipse, what can I do further?
Yes you can delete the /etc/eclipse.ini file without causing any issues in your system.
Additionally, Eclipse stores personal files (workspace configuration, plugin info etc.) under .eclipse folder in your home directory which may not be removed when you are performing the uninstall.
Assuming you are the only user using eclipse on that machine you may issue the following command to completely remove all personal config files.
rm -rf ~/.eclipse

Portable Eclipse Juno with plugins

I am currently trying to make an Eclipse istallation with installed plugins portable, so that you only have to copy the whole "eclipse"-folder to another system and have the same setup as on the original system.
My problem now is, that since eclipse 4.2 (?) when using Help > Install new Software... plugins are installed externally into the folder
C:/Users/Username/.eclipse/org.eclipse.platform_4.2.0_identifier
and not into the folder where the "eclipse.exe" is located:
C:/Program Files (x86)/eclipse
Now my question is if it is possible to make eclipse install additional plugins into the plugins/features-folder of eclipse's home folder (C:/Program Files (x86)/eclipse).
Unfortunately, it isn't possible to use the dropins-folder, because one plugin that shall be installed only exists as an update site.
I'm using
Windows 7 Professional Service Pack 1 64bit
with
Eclipse IDE for C/C++ Developers
Version: Juno Service Release 2
32-bit (to provide portability).
Greets :)
Do not put your eclipse installation under the "Program Files" folder. Eclipse will install all plugins to its own folder by default, unless that folder is not writable from Eclipse. And the "Program Files" folder should not be writable by you (unless you are using administrative access rights). Only the trusted installer service account should modify that folder (following Windows guidelines).
Therefore unzip Eclipse somewhere else into a location where anyone is allowed to write, install your plugins and zip the whole folder again.
As an alternative to that ZIP package you may want to look at File -> Export -> Install -> Software items to file, where you can export (and re-import) a list of your already installed plugins.
What mack is trying to do should work, this is essentially what the eclipse foundation do to provide the various distros.
The plugin that is only available as an update site could be installed into and existing in-installation then copied to the new distro. Only trick is making sure you have all the feature and plugin jar files.