- This topic has 6 replies, 3 voices, and was last updated 6 years, 8 months ago by
.
-
Posts
-
Applied the recent upgrade of CodeMix, and not the development team are dead in the water, because they can not get the Eclipse IDE to run. Attached is the log file generated for Eclipse Photon. We are trying to figure out how to back out the recent update so the development team can get back to work.
We found that we needed to force a clean start of Eclipse Photon. All users should be made aware that this update requires this. Temporarily place in the eclipse.ini as the first line the following:
-cleanOuch! From the log, it looks like you’ve hit a case where the provisioning layer of Eclipse (p2) didn’t correctly update bundles.info after installation.
Would it be possible to get the error log from the second launch where you used -clean? Specifically if you see messages about bundles.info in there.
We added in some logic to check consistency after CodeMix update in this update, so it unfortunately would only help in your next launch.
Thanks!
Attached is the log file from this morning before and with the after messages. A side effect of the recent CodeMix update has disabled the DevStyle launcher. No big deal, Eclipse reverted back to the original launcher.
Thanks Eric,
We’ve quickly pulled the update from the site while we investigate. And yes, -clean works as it triggers rewiring.
Good day Eric
In case of DevStyle launcher – even -clean wouldn’t help to re-enable it. To bring it back, please go to DevStyle Preference page – Window > Preferences > DevStyle and check “Use the Startup Experience” checkbox there, then hit “Apply and close”Thanks again for bringing this to our attention. We were able to identify a root cause (started with a bad update from CI 12a -> 13 causing duplicates in a bundles.info file. Your log helped identify the duplicate bundle that caused issues was from 12a. Whoops!
All that said, the fixed release correctly handles this situation as well, and even if there were duplicates, wouldn’t crash. Thanks again for quickly bringing this to our attention.
No need to take any action on your side.
