Community
Participate
Working Groups
1016 integration build, happens on aix ONLY - unzip a new eclipse, start it - "completing install" splash is shown - workbench comes up, but then so does a dialog saying that changes have been detected and the Update Manager can be opened (problem) -> just out of interest I opened the Update Manager and it showed nothing
Chirstophe, I guess this has been fixed in 2.0.2 stream and will be in HEAD when we merge, right?
no, seems related to bug 24942
Grant, can you confirm you reused an existing workspace ? or was that a complete full new install ?
It was a completely new install, including new workspace.
sounds very strange, cannot reproduce on Windows even with 1016 Grant, can you paste the .metadata directory and tell us what is the command line you used to start. I will send you the new updatecore.jar from today. If you can retry to install 1016 and before you start replace updatecore.jar I would appreciate
This only happens on aix. It doesn't happen on solaris or hpux (and assumedly not on linux and win32 either). My start line is: ./eclipse -vm /usr/java131/jre/bin/java I'll attach two zipped .metadata's: - The first shows its contents once the workbench has been brought up and the "Do you want to run the Update Manager?" prompter is showing. - The second shows its contents after saying Yes to this dialog and then pressing Cancel in the manager since it's empty.
Created attachment 2212 [details] .metadata with "Launch Update Manager?" prompter showing
Created attachment 2213 [details] .metadata after Update Manager has been closed
The problem still happens with the new updatecore.jar that was sent to me.
Hum, this is 2.1 code. Update hasn't released any code in 2.1 since 2.0.1 code Definitly an issue though... but probably buried in core on AIX... ok, can you copy .options from org.eclipse.update.core, change all values to true, and run again with -debug Sorry about the trouble of having you debug it. PS: the JAR I sent will not help you
hum, should have added cut and paste the output on the command line + the .log file Thanks
This scenario doesn't result in a .log file being generated in workspace/.metadata I'll attach the output of running Eclipse with -debug after all core update .options have been set to true.
Created attachment 2216 [details] output of running with -debug and all core update .options set to true
Sorry, I didn't copy the .options to the eclipse root directory. The output I got this time was much more extensive. I'll attach it.
Created attachment 2217 [details] second try
Here's the .log that was generated...
Created attachment 2219 [details] .metadata/.log
It seems there is a problem renaming the platform.cfg.temp into platform.cfg file so the next time we try to save the platform.cfg.temp we seem to fail. we need to fix 1) why it seems we cannot rename platform.cfg.temp into platform.cfg 2) even if we cannot save the platform.cfg, the LocalSite save() should not fail I presume the log for bug 24997 would throw the same type of error. can you check ? Next Step: reproduce here and fix
Note that I've attached the .log and -debug output spews to bug 24997 .
Unable to reproduce with 2.1 and 2.0.2 Install SDK-I20021018-aix and SDK-M20021018-aix Started and saw the 'completing install' then the Eclipse Splash Screen The dialog about new updates doesn't show. The error seems double and we need to resolve them both. Contact Grant off line, try to reproduce with debug JAR file, post findings here after...
*** Bug 24997 has been marked as a duplicate of this bug. ***
Released code where: if the platform.cfg cannot be renamed, the reconciliation still occurs. the LocalSite.xml will be written and no dialog should show up saying changes have been detected. Upon retstart the platform realizes there is no platform.cfg will look for platfrom.cfg.tmp and find it. Unable to reproduce, please download tomorrow's integration build and test (2.0.2)
Verified that this no longer happens in today's 2.0.2 maintainence build.
