This patch allows application developers to run custom
code during the install process. Briefly, the
developer writes a class that provides static methods
that will be called by the package installer. Methods
are for pre-install, post-install, pre-upgrade,
post-upgrade, pre-uninstall, and post-uninstall. The
developer compiles the class and any classes/resources
that it uses that are not available in the
vainstall.jar file and packages them in a jar file.
The name of the class that provides static methods and
the name of the jar file are named in the vainstall
package configuration file. The package builder
passess the class name to the installer and extracts
classes/resources from the jar file for use by the
installer. The installer checks to see if a class name
has been provided, and if so, uses reflection to call
the appropriate methods at the appropriate times.
Methods have access to status components on the user
interface, and can reference useful global static
fields and methods.
Documentation is in src/doc/package_prepost.html.
Two structural changes have been made to Setup.java.
Creation of the package destination directory and
opening of the log of installed files have been moved
from the unzip method to the startInstall method so
that the directory and file log are available to the
preInstall method.
This patch is submitted to the developers of VAInstall
in the hope that they will incorporate it into the
package under their copyright.
The patch was made against the CVS tree as it stood on
25 Jan 2004. To apply the patch, have as the current
working directory the src directory of the CVS tree and
run
cat patch_file_name | patch -p1
Patch adds custom pre/post-processing to VAInstall
Logged In: YES
user_id=200680
Thanks for your job.
I've just committed the changes. I'm going to build the exe file for
windows tomorrow.
Logged In: NO
Could be done via Beanshell