Community
Participate
Working Groups
Created attachment 190806 [details] .log file I updated to: eclipse.buildId=I20110309-1400 java.version=1.6.0_24 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=fr_CA Command-line arguments: -os win32 -ws win32 -arch x86_64 -console and my workspace doesn't start anymore.
It looks like I20110309-1400 doesn't upgrade correctly. org.eclipse.e4.ui.workbench wasn't tagged, but that method changed from getContainingContext(MUIElement) to getContainingContext(MApplicationElement) in a different plugin that was tagged. The change was source compatible, but not binary compatible, and because workbench had the same qualifier the new version wasn't used in the p2 repo. I've tagged the bundle for the 22:00 build. The I20110309-1400 download is fine, because you get the newly compiled bundle. The
for I20110310-0100 PW
Right now I am trying to revert my workspace to the previous profile to be able to restart. I tried Kim's suggestion: C:\eclipse\3.7M4\eclipse\eclipsec.exe -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/eclipse/updates/4.1-I-builds -revert 1299541641319 -destination C:\eclipse\e4SDK\eclipse -profile SDKProfile -bundlepool C:\C:\eclipse\e4SDK\ -p2.os win32 -p2.ws win32 -p2.arch x86_64 but it doesn't work. Is this the right update site for 4.1 I builds? http://download.eclipse.org/eclipse/updates/4.1-I-builds Thanks.
(In reply to comment #3) > I tried Kim's suggestion: > C:\eclipse\3.7M4\eclipse\eclipsec.exe -application > org.eclipse.equinox.p2.director -repository > http://download.eclipse.org/eclipse/updates/4.1-I-builds -revert 1299541641319 > -destination C:\eclipse\e4SDK\eclipse -profile SDKProfile -bundlepool > C:\C:\eclipse\e4SDK\ -p2.os win32 -p2.ws win32 -p2.arch x86_64 your dest and bundlepool should be the same, right/ > > but it doesn't work. > Is this the right update site for 4.1 I builds? > http://download.eclipse.org/eclipse/updates/4.1-I-builds Yes, that's the correct site. That's the one that has the broken bundle. PW
Ok, it worked. I thought it failed, but the operation was still running. Thanks.
