|
| Re: Director produces broken eclipse.ini [message #489731 is a reply to message #488723] |
Mon, 05 October 2009 17:18   |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
This could be https://bugs.eclipse.org/bugs/show_bug.cgi?id=280007
and/or https://bugs.eclipse.org/bugs/show_bug.cgi?id=284303.
These were both upgrades, and you are removing the old install before
installing the new one. Perhaps the install/p2 directory is still there
so that it behaves like an upgade instead of a new install.
Daniel Jacobowitz wrote:
> I'm investigating an upgrade problem from several of our users. So far
> we haven't been able to reproduce it, so I can't take a debugger to it.
> Has anyone seen this problem with the director before?
>
> In each case, Eclipse 3.4 was previously installed. We remove it before
> starting the director, although it's possible some files were left behind.
>
> During installation, we unpack the director and an update site. We
> run the director to create a full Eclipse installation:
>
> java -jar plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar \
> -application org.eclipse.equinox.p2.director \
> -repository 'jar:file:/path/to/site.zip!/' \
> -data '/path/to/temp/workspace/for/logging' \
> -installIU productIU \
> -destination /path/to/install \
> -profile SGXXProfile \
> -profileProperties org.eclipse.update.install.features=true \
> -roaming -p2.os win32 -p2.ws win32 -p2.arch x86
>
> The destination directory ought to be empty at this point; but I suspect
> it isn't,
> for whatever reason. It definitely doesn't have the previous (Eclipse 3.4)
> eclipse.ini in it, because if I leave it there I get
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=284630.
>
> After a successful install eclipse.ini shows:
>
> -startup
> plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200 .v20090519
> -showsplash
> com.codesourcery.ide
> --launcher.XXMaxPermSize
> 256m
> -vmargs
> -Xms40m
> -Xmx256m
>
> But a failed upgrade looks like this instead:
>
> -startup
> ./../../../Documents and Settings/Username/Local
> Settings/Temp/121212.tmp/p2-director/configuration/org.eclip
> se.osgi/bundles/27/data/-1670178961/plugins/org.eclipse.equi
> nox.launcher_1.0.200.v20090520.jar
> --launcher.library
> ./../../../Documents and Settings/Username/Local
> Settings/Temp/121212.tmp/p2-director/configuration/org.eclip
> se.osgi/bundles/27/data/-1670178961/plugins/org.eclipse.equi
> nox.launcher.win32.win32.x86_1.0.200.v20090519
> -showsplash
> com.codesourcery.ide
> --launcher.XXMaxPermSize
> 256m
> -install
> C:/Program Files/CodeSourcery/Sourcery G++/eclipse
> -vmargs
> -Xms40m
> -Xmx256m
>
> As far as I've been able to work out, -install is a symptom, not the
> cause. The real problem must be that the launcher data for the target
> platform has been overwritten with the launcher data for the director;
> that causes Equinox to write out -install since it seems like the
> default is wrong. The only thing I've been able to think of is a race
> condition in updating eclipse.ini.
>
> Any idea what might cause this?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03492 seconds
] 
Search
Help
Register
Login
Home
