VB had a tool to build installers. However I suggest a different approach. Jabaco should have a "Jappstore" that can install and keep applications updated, including Jabaco itself.

At a low lever i suggest a simple package management system. A jabaco application is packaged in a zip-file with the jar and other files that is needed. Jabaco should have a launcher that is used to launch jabaco applications.

Rather then having registry keys a package should have Portland files to identify itself. When removing a package it portland files should remove.

This means we may have to port Portland to windows, making a tool that manages the corresponding registry keys.

The packages should also have a file with checksums of every installed file, version information and other useful stuff. This should be added to a (SQLite?) database. It should be possible to add, remove and verify a package from the command line.

The "Jappstore" application itself should be able to connect to repositories and download packages from there. Check out YUM for an example of such an application.

Unlike RPM I am more a fan of the KISS principle. Therefore stuff like script or executables inside the package that can execute during install should not be allowed. It should be a simple decompress and verify solution.

Also "Jappstore" needs a licence management solution of some kind. When the user buys something from within the store, it should download and install without bothering the user about license. Instead it should be able to query the appstore fore an appropriate license.

I also see the possibility of other stuff like single sign on (probably required for licence management) and online data storage.