|
The biggest challenge is error feedback that makes it's way back to the user on the desktop: Firewall issues. Authority issues. Compiler and component (prerequisites) failures. The progress in the installation process. All that needs to be communicated back to the user in an intelligible manner.How hard is it? You can do CommandCalls and gather the messages back?
Also, the installer needs to be something easy to script so that after the work is done to package it on the i there is just a minimum amount of stuff that needs to be scripted at the installer end to make it all work. IzPack seems pretty flexible and there might be some way to write some generic scripts that call the same routines on the i with the instructions being packaged and run at the i (in CL, probably).
I have just been musing about it today as I ran the ant scripts to build, jar and create the installer for tn5250j. Something I hope to look at soon.I spent some time a while back to write some "build these Eclipse projects using ant and ant4eclipse" tasks. Those build.xml-files are rather nasty :)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.