[izpack-users] Install Log file

Miraodb miraodb at hotmail.com
Thu Jul 20 10:15:42 CEST 2006


Hi Klaus,

It totally makes sense !
I agree with your thougths.

One thing, is the filename of the log file a fixed one  or can we add an
attribute for its name ? that would be quite nice. Something like

<variable name="InstallerFrame.writeLogfile" value="yes"
filename="toto.log"/>
If filename isn't set, then default is install.log

As for the rest, let's go for it.
I shall start the docu right away.

Cheers,
Fabrice
----- Original Message ----- 
From: "Bartz, Klaus" <Klaus.Bartz at coi.de>
To: <izpack-users at lists.berlios.de>
Sent: Thursday, July 20, 2006 10:01 AM
Subject: Re: [izpack-users] Install Log file


> Hi Fabrice,
> I tend to give the installation creator and not the installation user
> the possibility to create install.log outside uninstaller.jar.
> At installation time the user often do not know whether he/she need
> a log file or not. But if there are problems and the user open a
> call to the hotline, may be the hotline needs the informations.
> If the adjudication to write a logfile is by the user, the hotline
> often will have bad luck.
> Additional it is easier to change not the GUI.
> Therefore I vote for a IzPanel variable driven logfile creation
> in InstallFrame.writeUninstallData().
> May be it will be more consistent to declare a new element in the
> info section of the installation.dtd, but this way will need much
> more work. Therefore
>
> <variable name="InstallerFrame.writeLogfile" value="yes"/>
>
> Impl then a ten minutes job.
>
> Cheers
>
> Klaus
>
>
> >-----Original Message-----
> >From: izpack-users-bounces at lists.berlios.de
> >[mailto:izpack-users-bounces at lists.berlios.de]On Behalf Of Miraodb
> >Sent: Thursday, July 20, 2006 9:39 AM
> >To: izpack-users at lists.berlios.de
> >Subject: Re: [izpack-users] Install Log file
> >
> >
> >Hi Klaus,
> >
> >Context related...
> >
> >> may be I understand not right...
> >I wasn't clear enough sorry...
> >
> >> I think to add a text area is not the solution because James needs
> >> the logging post mortem of the installation. In the InstallPanel the
> >> current installed file will by shown in a label above the
> >progressbar,
> >> but often it is so fast that nobody can read it.
> >
> >It's true that it oftens goes too fast, but once the installpanel has
> >finished and before clicking next, we could have a button for
> >saving the
> >log. That would do the job.
> >
> >> A text area with a
> >> scroll bar will be very big (4681 lines at my server installation).
> >> But I also think that it will be a good idea to duplicate install.log
> >> into the file system because some user have problems to
> >extract something
> >> out of a jar file.
> >> The impl should be peanuts. I vote for a facultative feature
> >controlled
> >> by an IzPack variable.
> >
> >This is another nice solution. Just pick up which one ever you
> >think is the
> >best. If we choose the second one then i vote for adding a checkbox on
> >finishpanel to open or not the log that has been created
> >automatically by
> >installpanel.
> >If you need code i have something for it...
> >
> >> May be we can split the work. I make the implementation, you
> >the docu :-)
> >> By the way, I write a short description of the summary stuff
> >and send it
> >> next week to you.
> >
> >No problem, I'll do the docu as soon as we decided which one
> >to use and how.
> >
> >Cheers,
> >Fabrice
> >
> >_______________________________________________
> >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