[izpack-users] Install Log file
Darren Govoni
darren at ontrenet.com
Thu Jul 20 19:38:06 CEST 2006
That's really great Klaus!!! Many thanks.
Darren
Bartz, Klaus wrote:
> Hi Darren,
> next week I check in a mimik which writes the
> file log into a separate file which path can be configured.
> But in the moment I will not add the log4j stuff because then
> the jar file has to be included into the installation jar
> and then it will expand about 219 KB.
> What will be locked you can see in uninstaller.jar#install.log.
>
> Additional you can use the Debug class, the Summary stuff and the
> logfile of AntActionInstallerListener and ProcessPanel.
>
> Cheers
>
> Klaus
>
>
>> -----Original Message-----
>> From: izpack-users-bounces at lists.berlios.de
>> [mailto:izpack-users-bounces at lists.berlios.de]On Behalf Of
>> Darren Govoni
>> Sent: Thursday, July 20, 2006 3:31 PM
>> To: izpack-users at lists.berlios.de
>> Subject: Re: [izpack-users] Install Log file
>>
>>
>> It's a very good idea. We've been wanting this ability for months and
>> its enormously
>> helpful in multiple ways for the minimal effort to add it.
>>
>> Heck, even a simple log4j INFO trace of what files where installed/etc
>> placed in the install directory
>> would go a million miles.....
>>
>> Miraodb wrote:
>>
>>> Hi Klaus and James,
>>>
>>> Few things on the topic...
>>> I saw many times in installers the possibility to have the files list
>>> automatically showing up dynamically as the install panel
>>>
>> goes on with the
>>
>>> packs... Couldn't we add a text area to show those files
>>>
>> while processed
>>
>>> (while they're written into install.log i guess...)? I could
>>>
>> create a copy
>>
>>> of installpanel which just add this and it's up to the
>>>
>> developer to choose
>>
>>> which installpanel to use ?
>>> Or we could also add a checkbox to the current panel to show
>>>
>> up or not the
>>
>>> text area... i'm not sure on how easy that is (dynamic
>>>
>> panels! never done
>>
>>> it)
>>>
>>> Solution 1 is easier i think. Two is a bit better. But most
>>>
>> importantly:
>>
>>> Sounds doable ? Sounds like a good idea?
>>>
>>> Any comments is appreciated.
>>>
>>> Cheers,
>>> Fabrice
>>>
>>> ----- Original Message -----
>>> From: "Bartz, Klaus" <Klaus.Bartz at coi.de>
>>> To: <izpack-users at lists.berlios.de>
>>> Sent: Thursday, July 20, 2006 8:31 AM
>>> Subject: Re: [izpack-users] Install Log file
>>>
>>>
>>>
>>>
>>>> Hi James,
>>>> see context related.
>>>>
>>>> Cheers
>>>>
>>>> Klaus
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: izpack-users-bounces at lists.berlios.de
>>>>> [mailto:izpack-users-bounces at lists.berlios.de]On Behalf Of
>>>>> James Oltmans
>>>>> Sent: Thursday, July 20, 2006 2:29 AM
>>>>> To: izpack-users at lists.berlios.de
>>>>> Subject: [izpack-users] Install Log file
>>>>>
>>>>>
>>>>> This has been asked before but I haven't seen any answers in the
>>>>> archives or clear documentation on the matter.
>>>>>
>>>>> Is there a way to create a log file during the
>>>>>
>> installation and save it
>>
>>>>> to a specific directory/location of my choosing?
>>>>>
>>>>>
>>>> Radio Erivan, principle yes, but...
>>>> If you use the SummaryPanel (really, I have forgotten to
>>>>
>> write something
>>
>>>> in the docu; sorry) you get a summary. Place it before the
>>>>
>> InstallPanel.
>>
>>>> If you also use the SummaryLoggerInstallerListener the file
>>>> $INSTALL_PATH/Uninstaller/InstallSummary.htm will be
>>>>
>> created after all
>>
>>>> chosen packs are installed.
>>>> The panel and the file contains the summary of all panels,
>>>>
>> but not the
>>
>>>> file set which was installed because this can be many (at my biggest
>>>> installation ~500KB).
>>>> The logging of installed files and created dirs are in the
>>>>
>>>>
>>> uninstaller.jar.
>>>
>>>
>>>> Extract install.log from the uninstaller.jar and you have it.
>>>>
>>>> If you create custom panels, you can determine what has to be placed
>>>> in the summary for that panel. You should implement the method
>>>> getSummaryBody. You can also implement getSummaryCaption, but there
>>>> is a default for it (see docu chapter "create your own panels" :-)).
>>>>
>>>>
>>>>
>>>>
>>>>> We'd like to be able to do post-mortem on what our
>>>>>
>> testers/users are
>>
>>>>> doing.
>>>>>
>>>>>
>>>> Uups, what do you install? A bomb? Or why your testers are
>>>>
>> die during
>>
>>>> installation :-)
>>>>
>>>>
>>>>
>>>>> Also, if that's possible is it also possible to add our own debug
>>>>> statements to the log?
>>>>>
>>>>> For instance:
>>>>> Beginning install
>>>>> Starting Pack X
>>>>> Installing somethingOrOther.jar to C:\Program
>>>>> Files\oh_my_what_the_heck_was_the_user_thinking\
>>>>> Finished Pack X
>>>>> Finished Install with errors:
>>>>> Blah blah blah
>>>>>
>>>>> We'd at least like to know what the user chose during the install
>>>>> process. Another very nice feature for the log file would
>>>>>
>> be hardware
>>
>>>>> info about the user.....
>>>>> Anything like that out there?
>>>>>
>>>>> Thanks
>>>>> James Oltmans
>>>>> _______________________________________________
>>>>> izpack-users mailing list
>>>>> izpack-users at lists.berlios.de
>>>>> http://bat.berlios.de/mailman/listinfo/izpack-users
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> izpack-users mailing list
>>>> izpack-users at lists.berlios.de
>>>> http://bat.berlios.de/mailman/listinfo/izpack-users
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> izpack-users mailing list
>>> izpack-users at lists.berlios.de
>>> http://bat.berlios.de/mailman/listinfo/izpack-users
>>>
>>>
>>>
>> _______________________________________________
>> izpack-users mailing list
>> izpack-users at lists.berlios.de
>> http://bat.berlios.de/mailman/listinfo/izpack-users
>>
>>
> _______________________________________________
> izpack-users mailing list
> izpack-users at lists.berlios.de
> http://bat.berlios.de/mailman/listinfo/izpack-users
>
>
More information about the izpack-users
mailing list