Re: [Installbase-devel] InstallBase 1.0a3 and recursive file groups

[Michael S. <ms...@cb...>]

On Fri, 11 Oct 2002, Damon Courtney wrote:

>     Hrmm..  There definitely SHOULD be a better way. 0-]  I will add
> something like this to my TODO list.  Maybe have an option to popup
> a window when adding directory structures that asks the base-level
> directory to add to.

Yeah. Ideally the whole thing would go in as one File Group, and you could
set the install root of the tree inside it.

>     In the meantime, the easiest way I can think of to do it would be
> to copy the whole jvm/ tree into any empty subdirectory called and
> then drop/add that directory.  The empty directory will be installed
> in <InstallDir>, and the subdirectory will automatically be created as
> <InstallDir>/jvm with all the rest of the tree following suit. 0-]

Close - since I need a different set of JVM files for each platform, I'd
have to give each parent directory a different name ("jvmwin", "jvmlin",
etc.) in the final install tree. Which would work, but what I ended up
doing was throwing together a Windows install to see how things work, and
doing lots of right-clicking. :)

> I would figure that especially for a Java project, InstallShield MP
> would do a better job, since it can do all the fancy Java stuff.

All it really takes care of is finding a JVM on the user's system if one
(with the proper versioning) is already installed, and installing a
bundled one if not. Since we use the latest JDK, it'd end up being
installed most of the time anyway - so I just have InstallBase copy it
over, no matter what.


At the end of the install (on Windows 2000), right before I clicked the
Finish button, I once got an error about not being able to delete
blank.zip from the temporary directory (permission denied). None of the
shortcuts were created and the temp dir was left behind after. I haven't
been able to duplicate it since - any idea what might have caused it?

"Permission Denied" doesn't make sense since I was Administrator. Might
have been a sharing violation since I had a filesystem Explorer window
open at the time, but it wasn't looking at anything near Administrator's
local settings folder at the time.


Thanks again,
Mike