Home » Eclipse Projects » Equinox » Issue installing particular feature configuration with p2
| Issue installing particular feature configuration with p2 [message #117726] |
Fri, 19 September 2008 07:54  |
 Tom Tabanao
Messages: 2
Registered: July 2009 |
Junior Member |
|
|
Hello,
I'm having difficulty deploying a feature patch to a Ganymede installation
via an update site when the feature contains a specific combination of
plugins.
I have two plugins, let's call them A and B, and they are provided by a
feature, F. This feature and these plugins are elsewhere on the
filesystem and associated with the Eclipse installation through the
"links" folder. I created a Feature Patch, F*, which contains new
versions of A and B (A* and B*). When I go through the Software Updates
menu and try to install F*, nothing seems to happen. The wizard looks
like it's doing something, but the end result is that nothing is deployed.
The features/plugins aren't on disk and aren't listed in the About menu.
Now the odd thing is (well, odd to me anyway), if I modify F* to provide
only A* or only B*, the feature patch (and whichever plugin is included)
will install correctly. Another oddity is that if I open the Software
Updates menu, add a new site, point it at the directory that contains F,
A, and B, install them to my Eclipse installation, then try to install F*
(with both A* and B* included) everything works correctly. Also,
installing F* on an Eclipse earlier than 3.4 works correctly.
Any clues as to what's going on, or even how to debug this on my own? The
Error Log view is empty post-install, and I've turned on the debug options
in Tracing with no luck. Let me know if there are any config files I can
provide that would help.
Thanks in advance,
Tom
|
|
|
| Re: Issue installing particular feature configuration with p2 [message #117786 is a reply to message #117726] |
Sat, 20 September 2008 17:57  |
Tom Tabanao
Messages: 2
Registered: July 2009 |
Junior Member |
|
|
I dug a little deeper into this (tracing through the p2 code) and I think
that this may have something to do with the plugins being singletons. If
I remove the singleton clauses from the end of the temp .opb file (before
sat4j gets its hands on it), my feature patch is correctly installed.
Another thing that I didn't mention in my first post is that I'm only
using a site.xml file for the update site at the moment. I tried
generating the p2 metadata (content/artifacts.xml) but didn't have any
luck with it either. I noticed that when the site.xml parser generates
the bundle info for the plugins in the feature patch, it generates a dummy
manifest and neglects to include that the updated plugins are singletons.
So when the Projector object compares the old plugin and the new plugin,
it seems to give preference to the old one because it thinks only the old
one is a singleton (I may be misinterpreting this logic).
It looks like content.xml conveys that the updated plugins are singletons,
but like I said, it didn't seem to help. I'm fairly sure the problem lies
somewhere around SimplePlanner.getProvisioningPlan() since the solution
generated by Projector doesn't include the feature patch or plugins
provided by the update site. Unfortunately the SAT problem isn't the
easiest thing in the world for me to debug (especially since it's spitting
out about 600 variables and 2500 constraints). :) Any suggestions?
Thanks,
Tom
Tom Tabanao wrote:
> Hello,
> I'm having difficulty deploying a feature patch to a Ganymede installation
> via an update site when the feature contains a specific combination of
> plugins.
> I have two plugins, let's call them A and B, and they are provided by a
> feature, F. This feature and these plugins are elsewhere on the
> filesystem and associated with the Eclipse installation through the
> "links" folder. I created a Feature Patch, F*, which contains new
> versions of A and B (A* and B*). When I go through the Software Updates
> menu and try to install F*, nothing seems to happen. The wizard looks
> like it's doing something, but the end result is that nothing is deployed.
> The features/plugins aren't on disk and aren't listed in the About menu.
> Now the odd thing is (well, odd to me anyway), if I modify F* to provide
> only A* or only B*, the feature patch (and whichever plugin is included)
> will install correctly. Another oddity is that if I open the Software
> Updates menu, add a new site, point it at the directory that contains F,
> A, and B, install them to my Eclipse installation, then try to install F*
> (with both A* and B* included) everything works correctly. Also,
> installing F* on an Eclipse earlier than 3.4 works correctly.
> Any clues as to what's going on, or even how to debug this on my own? The
> Error Log view is empty post-install, and I've turned on the debug options
> in Tracing with no luck. Let me know if there are any config files I can
> provide that would help.
> Thanks in advance,
> Tom
|
|
|
Goto Forum:
Current Time: Fri Sep 20 15:36:13 GMT 2024
Powered by FUDForum. Page generated in 0.03672 seconds |
] 
Search
Help
Register
Login
Home
