How to extend an install4j installation with a new Media file - install4j

We have had to add a new install medium to an install4j installation.
I can see two ways of updating the files on the distribution server.
Firstly, we could copy all the newly generated installation media and the new update.xml file. Here I have the question: in determining whether an update is necessary, is only the field "newVersion" used, or is the check sum also part of the logic?
Secondly, we could copy only the new medium and edit the update.xml with the new entry. This would be my prefered method as the newly generated versions of old install media would not have to be tested. The question is whether a hand edited update.xml is valid.

You can add a new entry to updates.xml manually. From the new compilation output, locate the entry for the new media file and insert it into the old updates.xml.

Related

How to implement a copy participant in eclipse to generate a new file along with other related files with same name within the same directory?

I'm trying to implement a copy participant and things work quite well when I copy a resource to another location. However, things does not work if I do a copy+paste into the same directory. Eclipse will happily suggest a new name for the file, but it seems that I cannot get a pointer to the new name in my implementation of the CopyParticipant.
What I see is, that org.eclipse.jdt.internal.corext.refactoring.changes.CopyResourceChange.getNewResourceName() asks for the new name but the participant appears to be already done with its job at that point in time. Did I miss something?

Can I change the order in updates.xml for media entries?

We have two media files in a project, one for 32bit and one for 64bit installer. 64bit entry is introduced now for a new version. I have noticed that the media build order can be changed in gui but the order for the entries that go to updates.xml doesn't seem to follow this order.
Is there some way the entries can be reordered for updates.xml? Currently the issue we are facing is that the previous version updater logic uses the first entry in the updates.xml and now it always points to the 64bit version as we cannot influence the order.
I have noticed that the media build order can be changed in gui but the order
for the entries that go to updates.xml doesn't seem to follow this order.
This is actually a bug, the order in updates.xml should be the same as in the list of media files.
It will be fixed shortly in 7.0.2, please contact support#ej-technologies.com to get a build where this is already fixed.

How to keep Folder/Files of extension in the uninstall process

I want to keep the all the file structure of extension when we uninstall any extension from the site.
In the uninstall process I want to remove DB tables only and want to keep all Files/Folders.
Can you please guide me if there is any solution.
Thanks
The manifest file for the extension includes a list of the relevant files that are installed for the extension. These can be copied from the website and zipped to recreate the install file for the extension.
Some extensions may also create associated data which you can back up by exporting relevant database tables and/or files (e.g. in the media or images folders).
A normal uninstall process (via Joomla! manage form) removes everything unless the extension has bug in its uninstall schedule. So, if you need to keep the files, uninstalling the extension won't be a good idea. I suggest you drop tables via phpMyAdmin instead.
To do that, go to your web hosting control panel (cPanel, DirectAdmin etc.) and look for the link to phpMyAdmin. Then select the database that contains your website data (if you got multiple databases and are not sure which one is the right one, you can check it via Joomla! admin > Global Configuration). When you found the database in phpMyAdmin, click on its name to go to its tables. Then select the table(s) of that specific extension by checking the checkbox(es) beside them. Then at the bottom of the all tables click "Drop". In the popup window click "OK" and the table(s) will be removed without effecting your folders/files.
I suggest you get a backup of your whole website first, if you're new to phpMyAdmin.
Be careful!

How to put Rule(check) on installation of certain set of files/folders?

Like in InstallWhere we put rule over the installation step of files and folders. How could we achieve the same in Install4j. Like it should check the value of some installer variable before installing the file. Please help in this regard.
Thanks!
You can create different file sets in the Files->Define Distribution Tree step. Each file set has an ID. IDs can be shown by toggling the "Show IDs" tool bar button.
In the installer, you can then call
context.getFileSetById("[ID]").setSelected(false)
on order to not install the files in the file set, where [ID] is replaced by the actual ID of the file set.

AnkhSVN - keep local copy and get latest version

I m new to use ankhSVN and having issues. I have created some new files which are not commited. It was required that i need to get latest version. I right clicked the folder and selected update. I didnt get the latest version and also my files were not present. It had a question mark icon towards the left.
Ideally i want to know what is the procedure to use ankhSVN.
Thanks and regards,
Ashish Agarwal
Ashish.Agarwal#Renishaw.com
[Unrelated: Please remove your e-mail address from your question if you don't want to receive spam.. you can be notified on updates via RSS and mail via your profile settings].
The 'folders' you see in Visual Studio are not normal folders/directories. They are just filters on your project. For some project types they map to actual folders (E.g. C#, VB and websites), but for other projects they don't (E.g. C, C++, Setup, Database, ...).
So actually you are just updating the selection of the filter/folder and everything below.
For most tasks you should always update on either the solution, the project level or a single file, as updating a subdirectory without the project referencing the files inside is an operation that can leave you with a broken project. (New files won't be included in your project and old files won't be removed).
AnkhSVN allows you to update the whole directory at once by checking the [X] Recursive checkbox at the bottom of the dialog, but this is currently not the default setting.