Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » get p2 to recognize an updated plugin
get p2 to recognize an updated plugin [message #489681] Mon, 05 October 2009 14:32 Go to next message
James Blackburn is currently offline James BlackburnFriend
Messages: 36
Registered: July 2009
Member
Hi All,

I'm trying to get p2 to pick up a modified version of a platform plugin which I build using pde headless builder. Unfortunately no matter what I do it refuses to install the bundle:

Cannot complete the install because of a conflicting dependency.
Software being installed: Broadcom CDT Feature 1.1.0.200910021642 (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
Software currently installed: Eclipse Platform 3.5.1.M20090917-0800 (org.eclipse.platform.ide 3.5.1.M20090917-0800)
Only one of the following can be installed at once:
Eclipse IDE UI 3.100.0.200910021642 (org.eclipse.ui.ide 3.100.0.200910021642)
Eclipse IDE UI 3.5.1.M20090826-0800 (org.eclipse.ui.ide 3.5.1.M20090826-0800)
Cannot satisfy dependency:
From: Broadcom CDT Feature 1.1.0.200910021642 (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
To: org.eclipse.ui.ide [3.100.0.200910021642]
Cannot satisfy dependency:
From: Eclipse Platform 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7 (org.eclipse.platform.feature.group 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7)
To: org.eclipse.ui.ide [3.5.1.M20090826-0800]
Cannot satisfy dependency:
From: Eclipse Platform 3.5.1.M20090917-0800 (org.eclipse.platform.ide 3.5.1.M20090917-0800)
To: org.eclipse.platform.feature.group [3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7]

I know that the bundle I'm installing is API compatible with the platform's bundle.

Is there any way of getting p2 to pick up my bundle in preference to the platform's bundle without rebuilding all of platform?

Cheers,
James
Re: get p2 to recognize an updated plugin [message #489693 is a reply to message #489681] Mon, 05 October 2009 14:57 Go to previous messageGo to next message
James Blackburn is currently offline James BlackburnFriend
Messages: 36
Registered: July 2009
Member
Actually I've just found Andrew Niefer's blog on Feature patches:
http://aniefer.blogspot.com/2009/06/patching-features-with-p 2.html
This looks like just what I'm looking for.

Cheers,
James

James Blackburn wrote:
> Hi All,
>
> I'm trying to get p2 to pick up a modified version of a platform plugin
> which I build using pde headless builder. Unfortunately no matter what
> I do it refuses to install the bundle:
>
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Broadcom CDT Feature 1.1.0.200910021642
> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
> Software currently installed: Eclipse Platform 3.5.1.M20090917-0800
> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
> Only one of the following can be installed at once: Eclipse IDE UI
> 3.100.0.200910021642 (org.eclipse.ui.ide 3.100.0.200910021642)
> Eclipse IDE UI 3.5.1.M20090826-0800 (org.eclipse.ui.ide
> 3.5.1.M20090826-0800)
> Cannot satisfy dependency:
> From: Broadcom CDT Feature 1.1.0.200910021642
> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
> To: org.eclipse.ui.ide [3.100.0.200910021642]
> Cannot satisfy dependency:
> From: Eclipse Platform
> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7
> (org.eclipse.platform.feature.group
> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7)
> To: org.eclipse.ui.ide [3.5.1.M20090826-0800]
> Cannot satisfy dependency:
> From: Eclipse Platform 3.5.1.M20090917-0800 (org.eclipse.platform.ide
> 3.5.1.M20090917-0800)
> To: org.eclipse.platform.feature.group
> [3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7]
>
> I know that the bundle I'm installing is API compatible with the
> platform's bundle.
>
> Is there any way of getting p2 to pick up my bundle in preference to the
> platform's bundle without rebuilding all of platform?
>
> Cheers,
> James
Re: get p2 to recognize an updated plugin [message #489734 is a reply to message #489693] Mon, 05 October 2009 17:24 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
You can also see part 2
http://aniefer.blogspot.com/2009/06/patching-features-part-2 .html
And Andrew Eisenberg's
http://contraptionsforprogramming.blogspot.com/2009/09/groov y-eclipse-plugin-now-supports.html

James Blackburn wrote:
> Actually I've just found Andrew Niefer's blog on Feature patches:
> http://aniefer.blogspot.com/2009/06/patching-features-with-p 2.html
> This looks like just what I'm looking for.
>
> Cheers,
> James
>
> James Blackburn wrote:
>> Hi All,
>>
>> I'm trying to get p2 to pick up a modified version of a platform
>> plugin which I build using pde headless builder. Unfortunately no
>> matter what I do it refuses to install the bundle:
>>
>> Cannot complete the install because of a conflicting dependency.
>> Software being installed: Broadcom CDT Feature 1.1.0.200910021642
>> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
>> Software currently installed: Eclipse Platform 3.5.1.M20090917-0800
>> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
>> Only one of the following can be installed at once: Eclipse IDE UI
>> 3.100.0.200910021642 (org.eclipse.ui.ide 3.100.0.200910021642)
>> Eclipse IDE UI 3.5.1.M20090826-0800 (org.eclipse.ui.ide
>> 3.5.1.M20090826-0800)
>> Cannot satisfy dependency:
>> From: Broadcom CDT Feature 1.1.0.200910021642
>> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
>> To: org.eclipse.ui.ide [3.100.0.200910021642]
>> Cannot satisfy dependency:
>> From: Eclipse Platform
>> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7
>> (org.eclipse.platform.feature.group
>> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7)
>> To: org.eclipse.ui.ide [3.5.1.M20090826-0800]
>> Cannot satisfy dependency:
>> From: Eclipse Platform 3.5.1.M20090917-0800
>> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
>> To: org.eclipse.platform.feature.group
>> [3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7]
>>
>> I know that the bundle I'm installing is API compatible with the
>> platform's bundle.
>>
>> Is there any way of getting p2 to pick up my bundle in preference to
>> the platform's bundle without rebuilding all of platform?
>>
>> Cheers,
>> James
Re: get p2 to recognize an updated plugin [message #489939 is a reply to message #489734] Tue, 06 October 2009 14:25 Go to previous messageGo to next message
James Blackburn is currently offline James BlackburnFriend
Messages: 36
Registered: July 2009
Member
Andrew Niefer wrote:
> You can also see part 2
> http://aniefer.blogspot.com/2009/06/patching-features-part-2 .html
> And Andrew Eisenberg's
> http://contraptionsforprogramming.blogspot.com/2009/09/groov y-eclipse-plugin-now-supports.html

Thanks Andrew. Unfortunately this doesn't appear to work if p2 is generating the metadata itself. I want the feature patch to match the platform feature 3.5.x.

My feature patch contains this:
<requires>
<import feature="org.eclipse.platform" version="3.5" patch="true"/>
</requires>

My plugins & features are built and installed into a raw extension location directory:
eclipse/.eclipseextension
eclipse/features/...
eclipse/plugins/...

Note I don't generate any p2 metadata.

When I point p2 at this extension loc. (and I assume it generates metadata on the fly) it says:

Cannot complete the install because one or more required items could not be found.
Software being installed: Broadcom CDT Feature 1.1.0.200910061458 (com.broadcom.cdt.feature.feature.group 1.1.0.200910061458)
Missing requirement: Broadcom Platform Patch 1.0.0 (com.broadcom.platform.patch.feature.group 1.0.0) requires 'org.eclipse.platform.feature.group [3.5.0]' but it could not be found
Cannot satisfy dependency:
From: Broadcom CDT Feature 1.1.0.200910061458 (com.broadcom.cdt.feature.feature.group 1.1.0.200910061458)
To: com.broadcom.platform.patch.feature.group [1.0.0]


How can I make p2 accept the feature patch and install the feature?

Cheers,
James

>
>
> James Blackburn wrote:
>> Actually I've just found Andrew Niefer's blog on Feature patches:
>> http://aniefer.blogspot.com/2009/06/patching-features-with-p 2.html
>> This looks like just what I'm looking for.
>>
>> Cheers,
>> James
>>
>> James Blackburn wrote:
>>> Hi All,
>>>
>>> I'm trying to get p2 to pick up a modified version of a platform
>>> plugin which I build using pde headless builder. Unfortunately no
>>> matter what I do it refuses to install the bundle:
>>>
>>> Cannot complete the install because of a conflicting dependency.
>>> Software being installed: Broadcom CDT Feature 1.1.0.200910021642
>>> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
>>> Software currently installed: Eclipse Platform 3.5.1.M20090917-0800
>>> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
>>> Only one of the following can be installed at once: Eclipse IDE
>>> UI 3.100.0.200910021642 (org.eclipse.ui.ide 3.100.0.200910021642)
>>> Eclipse IDE UI 3.5.1.M20090826-0800 (org.eclipse.ui.ide
>>> 3.5.1.M20090826-0800)
>>> Cannot satisfy dependency:
>>> From: Broadcom CDT Feature 1.1.0.200910021642
>>> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
>>> To: org.eclipse.ui.ide [3.100.0.200910021642]
>>> Cannot satisfy dependency:
>>> From: Eclipse Platform
>>> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7
>>> (org.eclipse.platform.feature.group
>>> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7)
>>> To: org.eclipse.ui.ide [3.5.1.M20090826-0800]
>>> Cannot satisfy dependency:
>>> From: Eclipse Platform 3.5.1.M20090917-0800
>>> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
>>> To: org.eclipse.platform.feature.group
>>> [3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7]
>>>
>>> I know that the bundle I'm installing is API compatible with the
>>> platform's bundle.
>>>
>>> Is there any way of getting p2 to pick up my bundle in preference to
>>> the platform's bundle without rebuilding all of platform?
>>>
>>> Cheers,
>>> James
Re: get p2 to recognize an updated plugin [message #489940 is a reply to message #489939] Tue, 06 October 2009 14:35 Go to previous message
James Blackburn is currently offline James BlackburnFriend
Messages: 36
Registered: July 2009
Member
I suppose a better question might be: how do I headlessly generate enough p2 metadata that I can use a directory as an extension location using Michael Scharf's trick?
http://michaelscharf.blogspot.com/2009/02/p2-how-i-install-p lugins-in-extension.html

If I could do that, presumably I could then update the content.xml so the feature would be applicable to all of 3.5.x? As it stands, generating and updating the content.xml locally with:

/projects/firepath/tools/releases/eclipse/3.5.1-x86_64-base/ eclipse -nosplash -consolelog -clean -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator -metadataRepository file:`pwd` -metadataRepositoryName Bcom-CDT Update Site -artifactRepository file:`pwd` -artifactRepositoryName Bcom-CDT Artifacts -noDefaultIUs -source `pwd` -vmargs -Xmx256M

doesn't appear to satisfy the p2 engine...

Any pointers greatly appreciated.

Cheers,
James

James Blackburn wrote:
> Andrew Niefer wrote:
>> You can also see part 2
>> http://aniefer.blogspot.com/2009/06/patching-features-part-2 .html
>> And Andrew Eisenberg's
>> http://contraptionsforprogramming.blogspot.com/2009/09/groov y-eclipse-plugin-now-supports.html
>
>
> Thanks Andrew. Unfortunately this doesn't appear to work if p2 is
> generating the metadata itself. I want the feature patch to match the
> platform feature 3.5.x.
>
> My feature patch contains this:
> <requires>
> <import feature="org.eclipse.platform" version="3.5" patch="true"/>
> </requires>
>
> My plugins & features are built and installed into a raw extension
> location directory:
> eclipse/.eclipseextension
> eclipse/features/...
> eclipse/plugins/...
>
> Note I don't generate any p2 metadata.
>
> When I point p2 at this extension loc. (and I assume it generates
> metadata on the fly) it says:
>
> Cannot complete the install because one or more required items could not
> be found.
> Software being installed: Broadcom CDT Feature 1.1.0.200910061458
> (com.broadcom.cdt.feature.feature.group 1.1.0.200910061458)
> Missing requirement: Broadcom Platform Patch 1.0.0
> (com.broadcom.platform.patch.feature.group 1.0.0) requires
> 'org.eclipse.platform.feature.group [3.5.0]' but it could not be found
> Cannot satisfy dependency:
> From: Broadcom CDT Feature 1.1.0.200910061458
> (com.broadcom.cdt.feature.feature.group 1.1.0.200910061458)
> To: com.broadcom.platform.patch.feature.group [1.0.0]
>
>
> How can I make p2 accept the feature patch and install the feature?
>
> Cheers,
> James
>
>>
>>
>> James Blackburn wrote:
>>> Actually I've just found Andrew Niefer's blog on Feature patches:
>>> http://aniefer.blogspot.com/2009/06/patching-features-with-p 2.html
>>> This looks like just what I'm looking for.
>>>
>>> Cheers,
>>> James
>>>
>>> James Blackburn wrote:
>>>> Hi All,
>>>>
>>>> I'm trying to get p2 to pick up a modified version of a platform
>>>> plugin which I build using pde headless builder. Unfortunately no
>>>> matter what I do it refuses to install the bundle:
>>>>
>>>> Cannot complete the install because of a conflicting dependency.
>>>> Software being installed: Broadcom CDT Feature 1.1.0.200910021642
>>>> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
>>>> Software currently installed: Eclipse Platform 3.5.1.M20090917-0800
>>>> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
>>>> Only one of the following can be installed at once: Eclipse IDE
>>>> UI 3.100.0.200910021642 (org.eclipse.ui.ide 3.100.0.200910021642)
>>>> Eclipse IDE UI 3.5.1.M20090826-0800 (org.eclipse.ui.ide
>>>> 3.5.1.M20090826-0800)
>>>> Cannot satisfy dependency:
>>>> From: Broadcom CDT Feature 1.1.0.200910021642
>>>> (com.broadcom.cdt.feature.feature.group 1.1.0.200910021642)
>>>> To: org.eclipse.ui.ide [3.100.0.200910021642]
>>>> Cannot satisfy dependency:
>>>> From: Eclipse Platform
>>>> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7
>>>> (org.eclipse.platform.feature.group
>>>> 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7)
>>>> To: org.eclipse.ui.ide [3.5.1.M20090826-0800]
>>>> Cannot satisfy dependency:
>>>> From: Eclipse Platform 3.5.1.M20090917-0800
>>>> (org.eclipse.platform.ide 3.5.1.M20090917-0800)
>>>> To: org.eclipse.platform.feature.group
>>>> [3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7]
>>>>
>>>> I know that the bundle I'm installing is API compatible with the
>>>> platform's bundle.
>>>>
>>>> Is there any way of getting p2 to pick up my bundle in preference to
>>>> the platform's bundle without rebuilding all of platform?
>>>>
>>>> Cheers,
>>>> James
Previous Topic:Extremely slow plug-in startup in 3.4 - 3.6M2 but not 3.3.2
Next Topic:modify the pre-trusted certificates used by the plug-in validator?
Goto Forum:
  


Current Time: Thu Mar 28 09:46:44 GMT 2024

Powered by FUDForum. Page generated in 0.03852 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top