I am trying to create an installer which will work as an installer in normal cases and if application is already installed it will update the existing installation.
I created an add-on installer with the new files. It works fine when executed independently.
To integrate it with the original installer, i merged this add-on installer with main installer .Then i checked if the app is already installed and added the "Add link to.." add-on installer.
But this installs all the files of the "Add on " as well as the main installer. Is this expected? As i am not even executing "Install Files" action of main installer. It installs the unnecessary files of original installer.
Is there any way to just execute the "Install files" action of only "Add-On" installer?
I am trying to create an installer which will work as an installer in normal cases and if
application is already installed it will update the existing installation.
Do not use an "Add-on installer" for that purpose. This is exactly what the regular installer does.
Related
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?
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?
This is the situation: I am the admin of a shared installation of Eclipse, and I want regular users (who do not have write-permission to the installation directory) to be able to update existing plugins. If they try this now they get an error saying something like:
"Your original request has been modified.
[Plugin name] will be ignored because it is already installed, and updates are not permitted.
..."
It works perfectly well for users to install new plugins, just not update existing ones.
Steps to reproduce:
Install Eclipse (I've tried, among others, Eclipse Classic 3.6.2 and
3.7, in Linux SUSE Enterprise 10).
As an admin with write-permission to the installation directory, install a plugin, e.g. EGit 1.0 from
http://download.eclipse.org/egit/updates-1.0
As a user (without
write-permission), try to install a newer version of the plugin (e.g.
EGit 1.3 from http://download.eclipse.org/egit/updates-1.3).
Perhaps related: If a regular user opens "About Eclipse SDK --> Installation Details --> Installed Software", the "Update" and "Uninstall" buttons are greyed out for every item on the list, though they are not for the admin.
So my questions are: Is this on purpose? and: Can I do something to allow users to update plugins?
I just have the same error. I removed the plugin of the update configuration file (but it's not the best solution)
%eclipse_home%\configuration\org.eclipse.update\platform.xml
This error is easily reproducible, install a plugin directly into the main configuration directory, and do a manual plugin install, like :
%eclipse_home%\eclipse.exe -configuration %eclipse_home%\configuration
Install > New software ...
So, the update will not working if you do that.
To correctly install a plugin, you just have to drop it into the "dropins" dir, like :
%eclipse_home%\configuration\dropins\yourplugindir
Then, the user could use it, or do an update
(init configuration) %eclipse_home%\eclipse.exe -initialize
(refresh workspace) %eclipse_home%\eclipse.exe -clean
%eclipse_home%\eclipse.exe
Install > New software ...
The Eclipse runtime options
Best regards,
Sorry for asking a question so similar to the last install4j question, but I have a similar problem. I need to package third party installers with my install4j installer that need to run before my application is installed. I'm currently unable to host the other packages, so the only option I see is to package them with my installer. Is there a way to do this?
Add the third-party installers on "Installer->Custom Code & Resources"
Add "Run executable" actions in your installer and reference the third-party installers with ${installer:sys.resourceDir}/executable.exe
I'm trying to install VCSupdate.zip in teamcity but the instructions online are for TeamCity 4. I'm using the newest version which is 5.1.2 so it doesn't have the data directory like the old one does. How do I install this plugin? Also, if i need to restart teamcity how do I do that?
Found it. The .zip files needs to be placed in the plugin folder which is found in your home directory .buildServer directory. To restart teamcity you can go into administrative tools and click on services on windows and click restart on teamcity server.