| eclipse.ini listing very specific plugins - problem when updating ? [message #336342] |
Tue, 09 June 2009 05:52  |
Eclipse User |
|
|
|
Originally posted by: max.andersen.redhat.com
Hi,
This might have been an old change but I just recently noticed it since
it caused our products not to launch properly on Galileo build.
eclipse.ini now contains 2 very specific plugin references:
-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
And if you don't list them eclipse won't start and we work around this
by using the specific names in the build.
So..
1) What is the reason for these two entries ? Why are they needed for
Galileo, but not for Ganymede ?
2) How is updates of these two entries handled by p2 ?
/max
|
|
|
| Re: eclipse.ini listing very specific plugins - problem when updating ? [message #336365 is a reply to message #336342] |
Tue, 09 June 2009 13:44  |
| Eclipse User |
|
|
|
In general, an install may contain multiple versions of the launchers.
Either because the install has been updated/reverted a few times, or
perhaps bundle pooling is being used and multiple products are sharing
the plugins folder.
The point of view of the launcher, these arguments are only strictly
necessary if the launchers aren't going to be found in the default
locations or if you don't want the highest version that is found.
However, p2 may be using these arguments (particularly on the mac) to
figure out what it needs to write in the config.ini
The metadata for a product is generally going to express a dependency on
a certain version of the launchers. The product will also include
configuration IUs that set the -startup and --launcher.library arguments
automatically.
p2 will automatically update the eclipse.ini based on the metadata.
For the SDK, to see the metadata that sets these arguments, look at the
highest versioned
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDK Profile.profile/*.profile
In there do a search on
toolingorg.eclipse.equinox.launcher
toolingorg.eclipse.equinox.launcher.win32.win32.x86
Max Rydahl Andersen wrote:
> Hi,
>
> This might have been an old change but I just recently noticed it since
> it caused our products not to launch properly on Galileo build.
>
> eclipse.ini now contains 2 very specific plugin references:
>
> -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
>
> And if you don't list them eclipse won't start and we work around this
> by using the specific names in the build.
>
> So..
>
> 1) What is the reason for these two entries ? Why are they needed for
> Galileo, but not for Ganymede ?
>
> 2) How is updates of these two entries handled by p2 ?
>
> /max
|
|
|
Powered by
FUDForum. Page generated in 0.02753 seconds
Home