| Summary: | Cannot launch dev workspace using I20080313-2106 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Dani Megert <daniel_megert> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | d.nachev, pascal, tjwatson |
| Version: | 3.4 | ||
| Target Milestone: | 3.4 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Dani Megert
Same using eclipse.exe Same when using fresh workspace. No config log. Mmmh, I assume (or at least hope) you tested your changes for this I-build? If so, can you give me a command line that works, since directly using java.exe is also broken, see bug 217788. Could it be a problem with extracting the build? I have similar happening to me on Mac and I remember one more guy complaining about this on Windows. Why? Does the build work for you on WindowsXP? If so, what's your command line? I have problems downloading the Windows build and could not try it out. There's a workaround: start using java.exe and provide "-ws win32" or hack the config.ini This is a sample entry from the eclipse.ini file: -startup /builds/I200803132106/src/I20080313-2106/p2temp/equinox.p2.build/sdk.install.win32/eclipse/plugins/org.eclipse.equinox.launcher_1.0.100.v20080303.jar Could this be a problem related to FrameworkAdmin? I worked around the issue by editing the eclipse.ini to the following -startup plugins/org.eclipse.equinox.launcher_1.0.100.v20080303.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080201a -showsplash org.eclipse.platform -vmargs -Xms40m -Xmx256m Basically remove all the absolute paths inserted during the build process. Interestingly enough you can update from one of this week I-build to this build and the dropins folder support will work. Fixed in build i0314-1059. Verified using I20080314-1059. |