| Shared install: private plug-ins not showing up [message #905936] |
Fri, 31 August 2012 06:38  |
Eclipse User |
|
|
|
Hi there,
I've previously asked this question in the platform group
(http://www.eclipse.org/forums/index.php/t/366962/) and was pointed here.
I'm trying to set up a shared install where the shared instance is a fully
initialized eclipse and the local instance is supposed to have additional
plug-ins installed on top. From my understanding, this is basically
"Scenario #3 - shared configuration" from
http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html&cp=2_1_3_7
The idea is to have a (basic) shared eclipse installation that can be used
either standalone by itself or as the basis for more specialized local
configurations with additional plug-ins installed on top (i.e. base eclipse
+ WTP, base eclipse + PHP, etc.)
What I'm after is a setup where
- The shared instance can be used and updated on its own
- Updates and additional plug-ins installed in the shared instance will be
visible in the local instances (i.e. the local instances "evolve" with the
shared instance)
- The local instances can install plug-ins on top of the shared instance
that are only visible to themselves
From my understanding, this is exactly what Scenario #3 accomplishes, with
one caveat: to be able to run, update and extend the shared install on its
own, it cannot actually be read-only in the filesystem (since the user is
the same in all cases)
What I tried was using a normal, non-read-only Eclipse installation for the
shared instance and run the local instances on top like this:
<shared>/eclipse.exe -vmargs \
-Dosgi.configuration.cascaded=true \
-Dosgi.configuration.area=<local>/configuration \
-Dosgi.sharedConfiguration.area=<shared>/configuration \
-Dosgi.sharedConfiguration.area.readOnly=true \
-Dosgi.install.area.readOnly=true
This seems to be working fine. The workspace comes up and all plug-ins from
the shared install are working properly. When I install stuff, it gets
installed into <local>/plugins and features. <local>/p2 and
<local>/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
get updated successfully, too.
However, after installing plug-ins into the local instance and restarting,
the new features are not available. I see them listed in Installation
Details -> Installed Software, but not in the Plug-Ins or Features lists or
the Plug-In Registry view (the Plug-Ins view does show them, though).
I get the same results when actually making the shared install read-only in
the filesystem, so I don't think that's the issue here.
Any ideas what goes wrong here? Or is there an altogether better way to
achieve this?
Best regards,
Carsten
|
|
|
|
|
|
| Re: Shared install: private plug-ins not showing up [message #1012177 is a reply to message #1012173] |
Wed, 20 February 2013 21:57  |
| Eclipse User |
|
|
|
My issue in particular is with the polarion subversion connectors for subversive. I include Subversive in my product, then when the user enables the subversion activity I defined, it walks them through the polarion connector discovery process. Everything works fine on windows. On linux, everything *appears* to work fine, no errors anywhere during the process, when you restart it no longer prompts you for a connector, the connectors show up in the installed software list, the features and plugins are in the user's config.dir, and bundles.info is properly updated. But the features and plugins are not available so subversive doesn't work. Gah! Any help or information at all would be very much appreciated. Thanks
[Updated on: Wed, 20 February 2013 21:59] by Moderator |
|
|
|
|
| Re: Shared install: private plug-ins not showing up [message #1012190 is a reply to message #1012185] |
Wed, 20 February 2013 22:46 |
| Eclipse User |
|
|
|
OK I just confirmed when I edit the shared install's bundles.info to contain the same new lines that got added to the user's local bundles.info file (to add the polarion connectors), then everything works fine. So I think there is indeed still a problem with cascaded shared installs on linux, but why it only occurs in my product and not plain vanilla eclipse I have no idea. Some arcane setting in the PDE build?
[Updated on: Wed, 20 February 2013 23:04] by Moderator |
|
|
Powered by
FUDForum. Page generated in 0.21213 seconds
Home