Re: [platform-update-dev] Change log for updates - is 5 levels enough?

[klicnik@xxxxxxxxxx]

We can consider increasing the number of histories maintained for F3. But changing the behavior (ie. "batching" more of the actions) is a larger change we would not do at this point. 

The original intent for the histories was to allow the user a limited "undo" of an install/ update operation that may be causing problems. Seems like it is now also being used as somewhat of a change activity log for service.

Pat McCarthy/Raleigh/IBM@IBMUS Sent by: platform-update-dev-admin@xxxxxxxxxxx 06/05/2002 08:54 AM Please respond to platform-update-dev

To:        platform-update-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-update-dev] Change log for updates - is 5 levels enough?

Based on testing it looks like the change log kept by the Update Manager remembers 5 changes.  We may need to consider increasing this 
number or packaging changes differently.

I started/stopped a base workbench, added a feature link file and started/stopped, added a 2nd feature link file and again started/stopped.

My change log file is full - any other mods and it will runeth over. Content below based on the system summary (I've added the ----- for
visibility):
Update Manager Log:

Configuration=Jun 4, 2002 11:53:14 AM
Current configuration=false

Date=Tue Jun 04 11:53:15 EDT 2002
Target=file:E:/Eclipse-int-06-02/eclipse/
Action="" installed
Status=Success

Date=Tue Jun 04 11:53:15 EDT 2002
Target=file:E:/Eclipse-int-06-02/eclipse/.config/platform.cfg.metadata/LocalSite.xml
Action="">
Status=Success

----------------------------------------------------
Configuration=Jun 4, 2002 11:56:02 AM
Current configuration=false

Date=Tue Jun 04 11:56:02 EDT 2002
Target=file:e:/Eclipse-int-06-02/GEF/Runtime/eclipse/
Action="" installed
Status=Success

Date=Tue Jun 04 11:56:02 EDT 2002
Target=file:E:/Eclipse-int-06-02/eclipse/
Action="" installed
Status=Success

Date=Tue Jun 04 11:56:03 EDT 2002
Target=file:E:/Eclipse-int-06-02/eclipse/workspace/.metadata/.config/platform.cfg.metadata/LocalSite.xml
Action="">
Status=Success

----------------------------------------------------
Configuration=Jun 4, 2002 11:56:35 AM
Current configuration=false

Date=Tue Jun 04 11:56:35 EDT 2002
Target=com.ibm.etools.gef_2.0.0
Action="">
Status=Success

----------------------------------------------------
Configuration=Jun 4, 2002 11:59:11 AM
Current configuration=false

Date=Tue Jun 04 11:59:11 EDT 2002
Target=file:e:/Eclipse-int-06-02/GEF/Runtime/eclipse/
Action="" installed
Status=Success

Date=Tue Jun 04 11:59:11 EDT 2002
Target=file:e:/Eclipse-int-06-02/GEF/Examples/eclipse/
Action="" installed
Status=Success

Date=Tue Jun 04 11:59:11 EDT 2002
Target=file:E:/Eclipse-int-06-02/eclipse/
Action="" installed
Status=Success

Date=Tue Jun 04 11:59:11 EDT 2002
Target=file:E:/Eclipse-int-06-02/eclipse/workspace/.metadata/.config/platform.cfg.metadata/LocalSite.xml
Action="">
Status=Success

----------------------------------------------------
Configuration=Jun 4, 2002 11:59:27 AM
Current configuration=true

Date=Tue Jun 04 11:59:27 EDT 2002
Target=com.ibm.etools.gef.examples.logicdesigner_2.0.0
Action="">
Status=Success

As soon as I maintain one of the linked (extension)features I loose visibility to the first two actions.  This seems to be due to the two-pass processing where each pass (install/reconcile and then enable) is a logged event.

Can we consider either doubling the number of log entries or managing the log such that an install/reconcile and then enable is one logged event?

Pat Mc.