Eddie Epstein wrote:
On 7/10/07, Michael Baessler <[EMAIL PROTECTED]> wrote:
So my plan was to clean the target installation directory before the new
PEAR file is installed to it. If the target install directory should be
cleaned can be specified with an additional parameter when using the
PEAR installer API.
Sounds good. Perhaps the additional [optional] parameter should only be
used when the target directory is *not* to be cleaned?
Yes, that parameter can prevent the deletion of the directory.
An known issue with that approach is, that after installing a PEAR file
to a directory, the same PEAR file cannot be installed again to the same
directory with the same JVM since the JVM has locked the jars so they
cannot be deleted when the directory for the next installation should be
cleaned. To do that, the JVM must be restarted, or another installation
directory must be used. The JVM locks the jar files when the
installation verification is executed.
Does this mean that currently the same PEAR file cannot be installed
into the
same directory from the same instance of runPearInstaller?
That's also what I thought first, but then I learned that on Windows the
files are "locked" from the JVM an cannot be deleted but they can be
updated or overridden.
Given this, the PEAR file can be installed again and again into the same
directory using the same instance of PearInstaller. I'm not sure if all
the resources are reloaded
from the JVM in the case also.
-- Michael
