Home » Eclipse Projects » Equinox » [P2] Updates treated as conflicts
| |
| Re: [P2] Updates treated as conflicts [message #134619 is a reply to message #134541] |
Tue, 07 July 2009 09:29   |
 Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
Hi Andrew,
I can understand what you explained, but I can't figure out how to fix
the problem.
My RCP app is made of 4 features. One top level feature that include the
3 others, and a feature-based product file that builds the top level
feature. (The .product file is in the top level feature)
How can I update the features AND the product, or specify unlimited
version ranges to always provides updates ?
Thanks.
Laurent.
Andrew Niefer a écrit :
> What is happening is that you have the product
> "com.sma.ui.em.product 1.1.5.200907061058" installed and now you are
> trying to also install "com.sma.feature.charts.feature.group
> 1.1.5.200907061109". These two things have conflicting requirements
> about the version of com.sma.ui.operation.gantt. This bundle is
> probably a singleton so only one version of it can be installed at once.
>
> I expect that your product is requiring an older version of the feature.
>
> What you want is a new version of the product which requires the new
> feature. Or you need the original version of the product to require a
> range of versions of the feature instead of just one particular version.
>
> This would also be why you aren't seeing any updates. The product is
> installed, not the feature, you don't have any updates to the product,
> only updates to the feature.
>
> -Andrew
>
> Laurent Marchal wrote:
>> Hi there !
>>
>> After days of trying to have my RCP application up-to-date with p2, i
>> finally get it working (I mean just have the p2 enabled app + update
>> site). The problem is when I use "Check for updates", no updates are
>> found, and when I go to "install new software" I see my features (even
>> if "hide items that are already installed" is check) and when i want
>> to install it I get :
>>
>> Your original request has been modified.
>> "Charts Plugins" is already installed, so an update will be
>> performed instead.
>> Cannot complete the install because of a conflicting dependency.
>> Software being installed: Charts Plugins 1.1.5.200907061109
>> (com.sma.feature.charts.feature.group 1.1.5.200907061109)
>> Software currently installed: Opcon/xps Enterprise Manager
>> 1.1.5.200907061058 (com.sma.ui.em.product 1.1.5.200907061058)
>> Only one of the following can be installed at once:
>> Gantt Plug-in 1.0.0.200907061109 (com.sma.ui.operation.gantt
>> 1.0.0.200907061109)
>> Gantt Plug-in 1.0.0.200907061058 (com.sma.ui.operation.gantt
>> 1.0.0.200907061058)
>>
>> I don't understand why p2 say that the plugin can not be updated
>> because it can be installed only once ? that's the goal of the update
>> ! and why I see my already installed features even with checked "hide
>> items that are already installed" ?
>>
>> Thanks.
>>
>> Laurent.
|
|
|
| Re: [P2] Updates treated as conflicts [message #134709 is a reply to message #134619] |
Tue, 07 July 2009 22:42 |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
I made an example here :
http://aniefer.blogspot.com/2009/07/composing-and-updating-c ustom-eclipse.html
Hopefully this helps.
-Andrew
Laurent Marchal wrote:
> Hi Andrew,
>
> I can understand what you explained, but I can't figure out how to fix
> the problem.
>
> My RCP app is made of 4 features. One top level feature that include the
> 3 others, and a feature-based product file that builds the top level
> feature. (The .product file is in the top level feature)
>
> How can I update the features AND the product, or specify unlimited
> version ranges to always provides updates ?
>
> Thanks.
> Laurent.
>
> Andrew Niefer a écrit :
>> What is happening is that you have the product
>> "com.sma.ui.em.product 1.1.5.200907061058" installed and now you are
>> trying to also install "com.sma.feature.charts.feature.group
>> 1.1.5.200907061109". These two things have conflicting requirements
>> about the version of com.sma.ui.operation.gantt. This bundle is
>> probably a singleton so only one version of it can be installed at once.
>>
>> I expect that your product is requiring an older version of the feature.
>>
>> What you want is a new version of the product which requires the new
>> feature. Or you need the original version of the product to require a
>> range of versions of the feature instead of just one particular version.
>>
>> This would also be why you aren't seeing any updates. The product is
>> installed, not the feature, you don't have any updates to the product,
>> only updates to the feature.
>>
>> -Andrew
>>
>> Laurent Marchal wrote:
>>> Hi there !
>>>
>>> After days of trying to have my RCP application up-to-date with p2, i
>>> finally get it working (I mean just have the p2 enabled app + update
>>> site). The problem is when I use "Check for updates", no updates are
>>> found, and when I go to "install new software" I see my features
>>> (even if "hide items that are already installed" is check) and when i
>>> want to install it I get :
>>>
>>> Your original request has been modified.
>>> "Charts Plugins" is already installed, so an update will be
>>> performed instead.
>>> Cannot complete the install because of a conflicting dependency.
>>> Software being installed: Charts Plugins 1.1.5.200907061109
>>> (com.sma.feature.charts.feature.group 1.1.5.200907061109)
>>> Software currently installed: Opcon/xps Enterprise Manager
>>> 1.1.5.200907061058 (com.sma.ui.em.product 1.1.5.200907061058)
>>> Only one of the following can be installed at once:
>>> Gantt Plug-in 1.0.0.200907061109 (com.sma.ui.operation.gantt
>>> 1.0.0.200907061109)
>>> Gantt Plug-in 1.0.0.200907061058 (com.sma.ui.operation.gantt
>>> 1.0.0.200907061058)
>>>
>>> I don't understand why p2 say that the plugin can not be updated
>>> because it can be installed only once ? that's the goal of the update
>>> ! and why I see my already installed features even with checked "hide
>>> items that are already installed" ?
>>>
>>> Thanks.
>>>
>>> Laurent.
|
|
|
| Re: [P2] Updates treated as conflicts [message #134801 is a reply to message #134709] |
Wed, 08 July 2009 12:32 |
Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
Thanks a lot Andrew, your explanations are really helpful !
In fact without your blog posts I could not get things working, for p2
or the pde build.
But for p2, I'm just discouraged. I have been working on updating my RCP
application since eclipse 3.4, and it's been months I am trying without
success. Each time, I have to spend days to learn and understand p2
concepts, and it does not suffice to make it work. I understand that, as
the new provisioning system, p2 needs to be able to make coffee and do
anything possible but for me it's just too complicated to use and it
drives me crazy.
I don't want to criticize the work p2 developer made, It just don't fit
my needs. p2 should be simple for easy things and complicated for
complex tasks. It's just : complicated.
I'm giving up p2, I will wait if someone find a decent solution for RCP
applications.
But once again, thanks for your help.
Laurent Marchal.
Andrew Niefer a écrit :
> I made an example here :
> http://aniefer.blogspot.com/2009/07/composing-and-updating-c ustom-eclipse.html
>
>
> Hopefully this helps.
>
> -Andrew
>
> Laurent Marchal wrote:
>> Hi Andrew,
>>
>> I can understand what you explained, but I can't figure out how to fix
>> the problem.
>>
>> My RCP app is made of 4 features. One top level feature that include
>> the 3 others, and a feature-based product file that builds the top
>> level feature. (The .product file is in the top level feature)
>>
>> How can I update the features AND the product, or specify unlimited
>> version ranges to always provides updates ?
>>
>> Thanks.
>> Laurent.
>>
>> Andrew Niefer a écrit :
>>> What is happening is that you have the product
>>> "com.sma.ui.em.product 1.1.5.200907061058" installed and now you are
>>> trying to also install "com.sma.feature.charts.feature.group
>>> 1.1.5.200907061109". These two things have conflicting requirements
>>> about the version of com.sma.ui.operation.gantt. This bundle is
>>> probably a singleton so only one version of it can be installed at once.
>>>
>>> I expect that your product is requiring an older version of the feature.
>>>
>>> What you want is a new version of the product which requires the new
>>> feature. Or you need the original version of the product to require
>>> a range of versions of the feature instead of just one particular
>>> version.
>>>
>>> This would also be why you aren't seeing any updates. The product is
>>> installed, not the feature, you don't have any updates to the
>>> product, only updates to the feature.
>>>
>>> -Andrew
>>>
>>> Laurent Marchal wrote:
>>>> Hi there !
>>>>
>>>> After days of trying to have my RCP application up-to-date with p2,
>>>> i finally get it working (I mean just have the p2 enabled app +
>>>> update site). The problem is when I use "Check for updates", no
>>>> updates are found, and when I go to "install new software" I see my
>>>> features (even if "hide items that are already installed" is check)
>>>> and when i want to install it I get :
>>>>
>>>> Your original request has been modified.
>>>> "Charts Plugins" is already installed, so an update will be
>>>> performed instead.
>>>> Cannot complete the install because of a conflicting dependency.
>>>> Software being installed: Charts Plugins 1.1.5.200907061109
>>>> (com.sma.feature.charts.feature.group 1.1.5.200907061109)
>>>> Software currently installed: Opcon/xps Enterprise Manager
>>>> 1.1.5.200907061058 (com.sma.ui.em.product 1.1.5.200907061058)
>>>> Only one of the following can be installed at once:
>>>> Gantt Plug-in 1.0.0.200907061109 (com.sma.ui.operation.gantt
>>>> 1.0.0.200907061109)
>>>> Gantt Plug-in 1.0.0.200907061058 (com.sma.ui.operation.gantt
>>>> 1.0.0.200907061058)
>>>>
>>>> I don't understand why p2 say that the plugin can not be updated
>>>> because it can be installed only once ? that's the goal of the
>>>> update ! and why I see my already installed features even with
>>>> checked "hide items that are already installed" ?
>>>>
>>>> Thanks.
>>>>
>>>> Laurent.
|
|
|
| Re: [P2] Updates treated as conflicts [message #134919 is a reply to message #134801] |
Wed, 08 July 2009 15:20 |
Eclipse User |
|
|
|
Originally posted by: fakemail.xyz.de
Laurent Marchal schrieb:
> Thanks a lot Andrew, your explanations are really helpful !
> In fact without your blog posts I could not get things working, for p2
> or the pde build.
>
> But for p2, I'm just discouraged. I have been working on updating my RCP
> application since eclipse 3.4, and it's been months I am trying without
> success. Each time, I have to spend days to learn and understand p2
> concepts, and it does not suffice to make it work. I understand that, as
> the new provisioning system, p2 needs to be able to make coffee and do
> anything possible but for me it's just too complicated to use and it
> drives me crazy.
>
> I don't want to criticize the work p2 developer made, It just don't fit
> my needs. p2 should be simple for easy things and complicated for
> complex tasks. It's just : complicated.
>
> I'm giving up p2, I will wait if someone find a decent solution for RCP
> applications.
>
> But once again, thanks for your help.
>
> Laurent Marchal.
somehow you speak from my heart
p2 has a much to steep learning curve currently.
Some concepts are not as clear as they should be.
Deprecating old updatemanager for eclipse itself migth have been a good
idea... though may be one should have waited another Version as for RCP
apps its hard. Especially I want to reemphasize the fact that I would
have also been unable to get p2 to work in RCP without Andrew's blog.
About updateing RCP apps.
It seems like there has been a concept change .
Before you updated the features and deployed them to the updatesite.
Now you update the product and then use the repository that you created
while exporting as update site.
You no longer add the features directly to an update site (you only do
this if the features are not contained in the product at least thats
how it seemed to me) now you add the product itself.
Adding just the features does not update the plugins in the product but
results in the problems you described.
(I know there was a lot of talk on the helpsites of the eclipse project
about the concept of Installable Units. Though this kind of behaviour
was not deducable from reading that for me.)
Christian
|
|
|
| Re: [P2] Updates treated as conflicts [message #135087 is a reply to message #134919] |
Thu, 09 July 2009 10:15 |
Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
Hello Christian,
Thanks for the clarification, the error is that I used the site.xml
with my top level feature inside, with the p2 publisher to generate the
update site. So the product itself could not be updated.
I understand better, and now when I make the update-site pointing
directly to the repository generated by the build, my RCP app detect
that an update is available for the product and all contained features.
The only problem is when p2 wants to download the files, it says : "no
repository found for ...."
An error occurred while collecting items to be installed
session context was:(profile=profile,
phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
operand=, action=).
No repository found containing:
osgi.bundle,com.sma.core,1.0.0.200907091056
No repository found containing:
osgi.bundle,com.sma.ui.administration,1.0.0.200907091056
No repository found containing:
osgi.bundle,com.sma.ui.administration.job,1.0.0.200907091056
All the features and plugins are there, but I think there should be an
URL somewhere in the content.xml/artifacts.xml that is pointing to local
files, because it was generated by the build, instead of the remote URL
of the update site.
I don't know how to tell p2 to publish the repository as an update site
? should I mirror it ?
Thanks.
Laurent.
Christian a écrit :
> Laurent Marchal schrieb:
>> Thanks a lot Andrew, your explanations are really helpful !
>> In fact without your blog posts I could not get things working, for p2
>> or the pde build.
>>
>> But for p2, I'm just discouraged. I have been working on updating my RCP
>> application since eclipse 3.4, and it's been months I am trying without
>> success. Each time, I have to spend days to learn and understand p2
>> concepts, and it does not suffice to make it work. I understand that, as
>> the new provisioning system, p2 needs to be able to make coffee and do
>> anything possible but for me it's just too complicated to use and it
>> drives me crazy.
>>
>> I don't want to criticize the work p2 developer made, It just don't fit
>> my needs. p2 should be simple for easy things and complicated for
>> complex tasks. It's just : complicated.
>>
>> I'm giving up p2, I will wait if someone find a decent solution for
>> RCP applications.
>>
>> But once again, thanks for your help.
>>
>> Laurent Marchal.
>
> somehow you speak from my heart
> p2 has a much to steep learning curve currently.
> Some concepts are not as clear as they should be.
> Deprecating old updatemanager for eclipse itself migth have been a good
> idea... though may be one should have waited another Version as for RCP
> apps its hard. Especially I want to reemphasize the fact that I would
> have also been unable to get p2 to work in RCP without Andrew's blog.
>
>
>
> About updateing RCP apps.
>
> It seems like there has been a concept change .
> Before you updated the features and deployed them to the updatesite.
>
> Now you update the product and then use the repository that you created
> while exporting as update site.
> You no longer add the features directly to an update site (you only do
> this if the features are not contained in the product at least thats
> how it seemed to me) now you add the product itself.
>
> Adding just the features does not update the plugins in the product but
> results in the problems you described.
> (I know there was a lot of talk on the helpsites of the eclipse project
> about the concept of Installable Units. Though this kind of behaviour
> was not deducable from reading that for me.)
>
> Christian
|
|
|
| Re: [P2] Updates treated as conflicts [message #135115 is a reply to message #135087] |
Thu, 09 July 2009 12:32 |
Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
I can install the RCP application directly from my update site using the
p2 agent without any problems. It's just the update that is not working,
I'm stuck with "No repository found" for all the bundles...
Laurent.
Laurent Marchal a écrit :
> Hello Christian,
>
> Thanks for the clarification, the error is that I used the site.xml
> with my top level feature inside, with the p2 publisher to generate the
> update site. So the product itself could not be updated.
>
> I understand better, and now when I make the update-site pointing
> directly to the repository generated by the build, my RCP app detect
> that an update is available for the product and all contained features.
>
> The only problem is when p2 wants to download the files, it says : "no
> repository found for ...."
>
> An error occurred while collecting items to be installed
> session context was:(profile=profile,
> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
> operand=, action=).
> No repository found containing:
> osgi.bundle,com.sma.core,1.0.0.200907091056
> No repository found containing:
> osgi.bundle,com.sma.ui.administration,1.0.0.200907091056
> No repository found containing:
> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907091056
>
>
> All the features and plugins are there, but I think there should be an
> URL somewhere in the content.xml/artifacts.xml that is pointing to local
> files, because it was generated by the build, instead of the remote URL
> of the update site.
>
> I don't know how to tell p2 to publish the repository as an update site
> ? should I mirror it ?
>
> Thanks.
> Laurent.
>
> Christian a écrit :
>> Laurent Marchal schrieb:
>>> Thanks a lot Andrew, your explanations are really helpful !
>>> In fact without your blog posts I could not get things working, for p2
>>> or the pde build.
>>>
>>> But for p2, I'm just discouraged. I have been working on updating my RCP
>>> application since eclipse 3.4, and it's been months I am trying without
>>> success. Each time, I have to spend days to learn and understand p2
>>> concepts, and it does not suffice to make it work. I understand that, as
>>> the new provisioning system, p2 needs to be able to make coffee and do
>>> anything possible but for me it's just too complicated to use and it
>>> drives me crazy.
>>>
>>> I don't want to criticize the work p2 developer made, It just don't fit
>>> my needs. p2 should be simple for easy things and complicated for
>>> complex tasks. It's just : complicated.
>>>
>>> I'm giving up p2, I will wait if someone find a decent solution for
>>> RCP applications.
>>>
>>> But once again, thanks for your help.
>>>
>>> Laurent Marchal.
>>
>> somehow you speak from my heart
>> p2 has a much to steep learning curve currently.
>> Some concepts are not as clear as they should be.
>> Deprecating old updatemanager for eclipse itself migth have been a
>> good idea... though may be one should have waited another Version as
>> for RCP apps its hard. Especially I want to reemphasize the fact that
>> I would have also been unable to get p2 to work in RCP without
>> Andrew's blog.
>>
>>
>>
>> About updateing RCP apps.
>>
>> It seems like there has been a concept change .
>> Before you updated the features and deployed them to the updatesite.
>>
>> Now you update the product and then use the repository that you
>> created while exporting as update site.
>> You no longer add the features directly to an update site (you only do
>> this if the features are not contained in the product at least thats
>> how it seemed to me) now you add the product itself.
>>
>> Adding just the features does not update the plugins in the product
>> but results in the problems you described.
>> (I know there was a lot of talk on the helpsites of the eclipse
>> project about the concept of Installable Units. Though this kind of
>> behaviour was not deducable from reading that for me.)
>>
>> Christian
|
|
|
| Re: [P2] Updates treated as conflicts [message #135224 is a reply to message #135115] |
Fri, 10 July 2009 07:30 |
Sergey Kuznetsov
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
Hello,
May be you can try to use repository exported with your product instead of
using update site project publisher. Just select "Generate metadata
repository" when you export your product - you'll get "repository" folder
and your product folder. Move product somewhere, move "repository" to your
web server or local site and set update site in your product to
"repository" folder, than export product once more (with new version or
qualifier) and replace old "repository" with a new one - now run "old"
product and check for update. If you did everything right - must work ;)
Sergey.
Laurent Marchal wrote:
> I can install the RCP application directly from my update site using the
> p2 agent without any problems. It's just the update that is not working,
> I'm stuck with "No repository found" for all the bundles...
> Laurent.
> Laurent Marchal a écrit :
>> Hello Christian,
>>
>> Thanks for the clarification, the error is that I used the site.xml
>> with my top level feature inside, with the p2 publisher to generate the
>> update site. So the product itself could not be updated.
>>
>> I understand better, and now when I make the update-site pointing
>> directly to the repository generated by the build, my RCP app detect
>> that an update is available for the product and all contained features.
>>
>> The only problem is when p2 wants to download the files, it says : "no
>> repository found for ...."
>>
>> An error occurred while collecting items to be installed
>> session context was:(profile=profile,
>> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
>> operand=, action=).
>> No repository found containing:
>> osgi.bundle,com.sma.core,1.0.0.200907091056
>> No repository found containing:
>> osgi.bundle,com.sma.ui.administration,1.0.0.200907091056
>> No repository found containing:
>> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907091056
>>
>>
>> All the features and plugins are there, but I think there should be an
>> URL somewhere in the content.xml/artifacts.xml that is pointing to local
>> files, because it was generated by the build, instead of the remote URL
>> of the update site.
>>
>> I don't know how to tell p2 to publish the repository as an update site
>> ? should I mirror it ?
>>
>> Thanks.
>> Laurent.
>>
>> Christian a écrit :
>>> Laurent Marchal schrieb:
>>>> Thanks a lot Andrew, your explanations are really helpful !
>>>> In fact without your blog posts I could not get things working, for p2
>>>> or the pde build.
>>>>
>>>> But for p2, I'm just discouraged. I have been working on updating my RCP
>>>> application since eclipse 3.4, and it's been months I am trying without
>>>> success. Each time, I have to spend days to learn and understand p2
>>>> concepts, and it does not suffice to make it work. I understand that, as
>>>> the new provisioning system, p2 needs to be able to make coffee and do
>>>> anything possible but for me it's just too complicated to use and it
>>>> drives me crazy.
>>>>
>>>> I don't want to criticize the work p2 developer made, It just don't fit
>>>> my needs. p2 should be simple for easy things and complicated for
>>>> complex tasks. It's just : complicated.
>>>>
>>>> I'm giving up p2, I will wait if someone find a decent solution for
>>>> RCP applications.
>>>>
>>>> But once again, thanks for your help.
>>>>
>>>> Laurent Marchal.
>>>
>>> somehow you speak from my heart
>>> p2 has a much to steep learning curve currently.
>>> Some concepts are not as clear as they should be.
>>> Deprecating old updatemanager for eclipse itself migth have been a
>>> good idea... though may be one should have waited another Version as
>>> for RCP apps its hard. Especially I want to reemphasize the fact that
>>> I would have also been unable to get p2 to work in RCP without
>>> Andrew's blog.
>>>
>>>
>>>
>>> About updateing RCP apps.
>>>
>>> It seems like there has been a concept change .
>>> Before you updated the features and deployed them to the updatesite.
>>>
>>> Now you update the product and then use the repository that you
>>> created while exporting as update site.
>>> You no longer add the features directly to an update site (you only do
>>> this if the features are not contained in the product at least thats
>>> how it seemed to me) now you add the product itself.
>>>
>>> Adding just the features does not update the plugins in the product
>>> but results in the problems you described.
>>> (I know there was a lot of talk on the helpsites of the eclipse
>>> project about the concept of Installable Units. Though this kind of
>>> behaviour was not deducable from reading that for me.)
>>>
>>> Christian
|
|
|
| Re: [P2] Updates treated as conflicts [message #135270 is a reply to message #135224] |
Fri, 10 July 2009 09:06 |
Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
Hi Sergey,
I did not use the update site publisher anymore, cause it will not work.
I usually not use the wizard to build the product (I use the headless
build) but I tried your suggestion and I get the same errors :
An error occurred while collecting items to be installed
session context was:(profile=profile,
phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
operand=, action=).
No repository found containing:
osgi.bundle,com.sma.core,1.0.0.200907101041
No repository found containing:
osgi.bundle,com.sma.ui.administration,1.0.0.200907101041
No repository found containing:
osgi.bundle,com.sma.ui.administration.job,1.0.0.200907101041
..... more errors
It's only an update problem. I am sure it's not coming from plugins that
can not be downloaded, because I can install the product using the p2
agent directly from the update site without any problems.
Thanks.
Laurent.
Sergey a écrit :
> Hello,
>
> May be you can try to use repository exported with your product instead
> of using update site project publisher. Just select "Generate metadata
> repository" when you export your product - you'll get "repository"
> folder and your product folder. Move product somewhere, move
> "repository" to your web server or local site and set update site in
> your product to "repository" folder, than export product once more (with
> new version or qualifier) and replace old "repository" with a new one -
> now run "old" product and check for update. If you did everything right
> - must work ;)
>
> Sergey.
>
> Laurent Marchal wrote:
>
>> I can install the RCP application directly from my update site using
>> the p2 agent without any problems. It's just the update that is not
>> working, I'm stuck with "No repository found" for all the bundles...
>
>> Laurent.
>
>> Laurent Marchal a écrit :
>>> Hello Christian,
>>>
>>> Thanks for the clarification, the error is that I used the
>>> site.xml with my top level feature inside, with the p2 publisher to
>>> generate the update site. So the product itself could not be updated.
>>>
>>> I understand better, and now when I make the update-site pointing
>>> directly to the repository generated by the build, my RCP app detect
>>> that an update is available for the product and all contained features.
>>>
>>> The only problem is when p2 wants to download the files, it says :
>>> "no repository found for ...."
>>>
>>> An error occurred while collecting items to be installed
>>> session context was:(profile=profile,
>>> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
>>> operand=, action=).
>>> No repository found containing:
>>> osgi.bundle,com.sma.core,1.0.0.200907091056
>>> No repository found containing:
>>> osgi.bundle,com.sma.ui.administration,1.0.0.200907091056
>>> No repository found containing:
>>> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907091056
>>>
>>>
>>> All the features and plugins are there, but I think there should be
>>> an URL somewhere in the content.xml/artifacts.xml that is pointing to
>>> local files, because it was generated by the build, instead of the
>>> remote URL of the update site.
>>>
>>> I don't know how to tell p2 to publish the repository as an update
>>> site ? should I mirror it ?
>>>
>>> Thanks.
>>> Laurent.
>>>
>>> Christian a écrit :
>>>> Laurent Marchal schrieb:
>>>>> Thanks a lot Andrew, your explanations are really helpful !
>>>>> In fact without your blog posts I could not get things working, for p2
>>>>> or the pde build.
>>>>>
>>>>> But for p2, I'm just discouraged. I have been working on updating
>>>>> my RCP
>>>>> application since eclipse 3.4, and it's been months I am trying
>>>>> without
>>>>> success. Each time, I have to spend days to learn and understand p2
>>>>> concepts, and it does not suffice to make it work. I understand
>>>>> that, as
>>>>> the new provisioning system, p2 needs to be able to make coffee and do
>>>>> anything possible but for me it's just too complicated to use and it
>>>>> drives me crazy.
>>>>>
>>>>> I don't want to criticize the work p2 developer made, It just don't
>>>>> fit
>>>>> my needs. p2 should be simple for easy things and complicated for
>>>>> complex tasks. It's just : complicated.
>>>>>
>>>>> I'm giving up p2, I will wait if someone find a decent solution for
>>>>> RCP applications.
>>>>>
>>>>> But once again, thanks for your help.
>>>>>
>>>>> Laurent Marchal.
>>>>
>>>> somehow you speak from my heart
>>>> p2 has a much to steep learning curve currently.
>>>> Some concepts are not as clear as they should be.
>>>> Deprecating old updatemanager for eclipse itself migth have been a
>>>> good idea... though may be one should have waited another Version as
>>>> for RCP apps its hard. Especially I want to reemphasize the fact
>>>> that I would have also been unable to get p2 to work in RCP without
>>>> Andrew's blog.
>>>>
>>>>
>>>>
>>>> About updateing RCP apps.
>>>>
>>>> It seems like there has been a concept change .
>>>> Before you updated the features and deployed them to the updatesite.
>>>>
>>>> Now you update the product and then use the repository that you
>>>> created while exporting as update site.
>>>> You no longer add the features directly to an update site (you only
>>>> do this if the features are not contained in the product at least
>>>> thats how it seemed to me) now you add the product itself.
>>>>
>>>> Adding just the features does not update the plugins in the product
>>>> but results in the problems you described.
>>>> (I know there was a lot of talk on the helpsites of the eclipse
>>>> project about the concept of Installable Units. Though this kind of
>>>> behaviour was not deducable from reading that for me.)
>>>>
>>>> Christian
>
>
|
|
|
| Re: [P2] Updates treated as conflicts [message #135298 is a reply to message #135270] |
Fri, 10 July 2009 10:33 |
Sergey Kuznetsov
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
Hi,
For me it looks like you didn't include all neccessary plugins for p2 can
get the job done. As for me I have one more feature project in my
product(s) where I collect all p2 stuff and include this feature in
product configuration. Here is the list (it works for me):
<plugin
id="org.eclipse.ecf.filetransfer"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.ui.sdk.scheduler"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.core"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.metadata"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.touchpoint.eclipse"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.artifact.repository"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.ui"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.engine"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.ecf"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.ecf.provider.filetransfer"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.ui.sdk"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.apache.commons.codec"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.ecf.provider.filetransfer.httpclient"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.repository"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.touchpoint.natives"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.ecf.identity"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.metadata.repository"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.apache.commons.httpclient"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.extensionlocation"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.updatesite"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.apache.commons.logging"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.garbagecollector"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.simpleconfigurator.manipulator"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.security.ui"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.directorywatcher"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.jarprocessor"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.frameworkadmin"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.security"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.director"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.updatechecker"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.frameworkadmin.equinox"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.publisher"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.sat4j.core"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.concurrent"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.p2.exemplarysetup"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.sat4j.pb"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.core.net"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.eclipse.equinox.common"
download-size="0"
install-size="0"
version="0.0.0"/>
Hope it helps,
Sergey.
Laurent Marchal wrote:
> Hi Sergey,
> I did not use the update site publisher anymore, cause it will not work.
> I usually not use the wizard to build the product (I use the headless
> build) but I tried your suggestion and I get the same errors :
> An error occurred while collecting items to be installed
> session context was:(profile=profile,
> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
> operand=, action=).
> No repository found containing:
> osgi.bundle,com.sma.core,1.0.0.200907101041
> No repository found containing:
> osgi.bundle,com.sma.ui.administration,1.0.0.200907101041
> No repository found containing:
> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907101041
> ..... more errors
> It's only an update problem. I am sure it's not coming from plugins that
> can not be downloaded, because I can install the product using the p2
> agent directly from the update site without any problems.
> Thanks.
> Laurent.
> Sergey a écrit :
>> Hello,
>>
>> May be you can try to use repository exported with your product instead
>> of using update site project publisher. Just select "Generate metadata
>> repository" when you export your product - you'll get "repository"
>> folder and your product folder. Move product somewhere, move
>> "repository" to your web server or local site and set update site in
>> your product to "repository" folder, than export product once more (with
>> new version or qualifier) and replace old "repository" with a new one -
>> now run "old" product and check for update. If you did everything right
>> - must work ;)
>>
>> Sergey.
>>
>> Laurent Marchal wrote:
>>
>>> I can install the RCP application directly from my update site using
>>> the p2 agent without any problems. It's just the update that is not
>>> working, I'm stuck with "No repository found" for all the bundles...
>>
>>> Laurent.
>>
>>> Laurent Marchal a écrit :
>>>> Hello Christian,
>>>>
>>>> Thanks for the clarification, the error is that I used the
>>>> site.xml with my top level feature inside, with the p2 publisher to
>>>> generate the update site. So the product itself could not be updated.
>>>>
>>>> I understand better, and now when I make the update-site pointing
>>>> directly to the repository generated by the build, my RCP app detect
>>>> that an update is available for the product and all contained features.
>>>>
>>>> The only problem is when p2 wants to download the files, it says :
>>>> "no repository found for ...."
>>>>
>>>> An error occurred while collecting items to be installed
>>>> session context was:(profile=profile,
>>>> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
>>>> operand=, action=).
>>>> No repository found containing:
>>>> osgi.bundle,com.sma.core,1.0.0.200907091056
>>>> No repository found containing:
>>>> osgi.bundle,com.sma.ui.administration,1.0.0.200907091056
>>>> No repository found containing:
>>>> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907091056
>>>>
>>>>
>>>> All the features and plugins are there, but I think there should be
>>>> an URL somewhere in the content.xml/artifacts.xml that is pointing to
>>>> local files, because it was generated by the build, instead of the
>>>> remote URL of the update site.
>>>>
>>>> I don't know how to tell p2 to publish the repository as an update
>>>> site ? should I mirror it ?
>>>>
>>>> Thanks.
>>>> Laurent.
>>>>
>>>> Christian a écrit :
>>>>> Laurent Marchal schrieb:
>>>>>> Thanks a lot Andrew, your explanations are really helpful !
>>>>>> In fact without your blog posts I could not get things working, for p2
>>>>>> or the pde build.
>>>>>>
>>>>>> But for p2, I'm just discouraged. I have been working on updating
>>>>>> my RCP
>>>>>> application since eclipse 3.4, and it's been months I am trying
>>>>>> without
>>>>>> success. Each time, I have to spend days to learn and understand p2
>>>>>> concepts, and it does not suffice to make it work. I understand
>>>>>> that, as
>>>>>> the new provisioning system, p2 needs to be able to make coffee and do
>>>>>> anything possible but for me it's just too complicated to use and it
>>>>>> drives me crazy.
>>>>>>
>>>>>> I don't want to criticize the work p2 developer made, It just don't
>>>>>> fit
>>>>>> my needs. p2 should be simple for easy things and complicated for
>>>>>> complex tasks. It's just : complicated.
>>>>>>
>>>>>> I'm giving up p2, I will wait if someone find a decent solution for
>>>>>> RCP applications.
>>>>>>
>>>>>> But once again, thanks for your help.
>>>>>>
>>>>>> Laurent Marchal.
>>>>>
>>>>> somehow you speak from my heart
>>>>> p2 has a much to steep learning curve currently.
>>>>> Some concepts are not as clear as they should be.
>>>>> Deprecating old updatemanager for eclipse itself migth have been a
>>>>> good idea... though may be one should have waited another Version as
>>>>> for RCP apps its hard. Especially I want to reemphasize the fact
>>>>> that I would have also been unable to get p2 to work in RCP without
>>>>> Andrew's blog.
>>>>>
>>>>>
>>>>>
>>>>> About updateing RCP apps.
>>>>>
>>>>> It seems like there has been a concept change .
>>>>> Before you updated the features and deployed them to the updatesite.
>>>>>
>>>>> Now you update the product and then use the repository that you
>>>>> created while exporting as update site.
>>>>> You no longer add the features directly to an update site (you only
>>>>> do this if the features are not contained in the product at least
>>>>> thats how it seemed to me) now you add the product itself.
>>>>>
>>>>> Adding just the features does not update the plugins in the product
>>>>> but results in the problems you described.
>>>>> (I know there was a lot of talk on the helpsites of the eclipse
>>>>> project about the concept of Installable Units. Though this kind of
>>>>> behaviour was not deducable from reading that for me.)
>>>>>
>>>>> Christian
>>
>>
|
|
|
| Re: [P2] Updates treated as conflicts [message #135377 is a reply to message #135298] |
Fri, 10 July 2009 12:49 |
Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
Hey,
I checked all the plugins listed here and I have exactly the same, in
fact I included the org.eclipse.equinox.p2.user.ui feature which
contains all these plugins. Except for org.apache.common.logging added
manually because it's missing in the p2 feature.
Thanks for the try, but I don't think the errors comes from there.
Laurent.
Sergey a écrit :
> Hi,
>
> For me it looks like you didn't include all neccessary plugins for p2
> can get the job done. As for me I have one more feature project in my
> product(s) where I collect all p2 stuff and include this feature in
> product configuration. Here is the list (it works for me):
>
> <plugin
> id="org.eclipse.ecf.filetransfer"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.ui.sdk.scheduler"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.core"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.metadata"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.touchpoint.eclipse"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.artifact.repository"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.ui"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.engine"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.ecf"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.ecf.provider.filetransfer"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.ui.sdk"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.apache.commons.codec"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.ecf.provider.filetransfer.httpclient"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.repository"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.touchpoint.natives"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.ecf.identity"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.metadata.repository"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.apache.commons.httpclient"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.extensionlocation"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.updatesite"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.apache.commons.logging"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.garbagecollector"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.simpleconfigurator.manipulator"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.security.ui"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.directorywatcher"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.jarprocessor"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.frameworkadmin"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.security"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.director"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.updatechecker"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.frameworkadmin.equinox"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.publisher"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.sat4j.core"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.concurrent"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.p2.exemplarysetup"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.sat4j.pb"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.core.net"
> download-size="0"
> install-size="0"
> version="0.0.0"
> unpack="false"/>
>
> <plugin
> id="org.eclipse.equinox.common"
> download-size="0"
> install-size="0"
> version="0.0.0"/>
>
> Hope it helps,
> Sergey.
>
> Laurent Marchal wrote:
>
>> Hi Sergey,
>
>> I did not use the update site publisher anymore, cause it will not
>> work. I usually not use the wizard to build the product (I use the
>> headless build) but I tried your suggestion and I get the same errors :
>
>
>> An error occurred while collecting items to be installed
>> session context was:(profile=profile,
>> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
>> operand=, action=).
>> No repository found containing:
>> osgi.bundle,com.sma.core,1.0.0.200907101041
>> No repository found containing:
>> osgi.bundle,com.sma.ui.administration,1.0.0.200907101041
>> No repository found containing:
>> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907101041
>> ..... more errors
>
>
>> It's only an update problem. I am sure it's not coming from plugins
>> that can not be downloaded, because I can install the product using
>> the p2 agent directly from the update site without any problems.
>
>> Thanks.
>> Laurent.
>
>
>> Sergey a écrit :
>>> Hello,
>>>
>>> May be you can try to use repository exported with your product
>>> instead of using update site project publisher. Just select "Generate
>>> metadata repository" when you export your product - you'll get
>>> "repository" folder and your product folder. Move product somewhere,
>>> move "repository" to your web server or local site and set update
>>> site in your product to "repository" folder, than export product once
>>> more (with new version or qualifier) and replace old "repository"
>>> with a new one - now run "old" product and check for update. If you
>>> did everything right - must work ;)
>>>
>>> Sergey.
>>>
>>> Laurent Marchal wrote:
>>>
>>>> I can install the RCP application directly from my update site using
>>>> the p2 agent without any problems. It's just the update that is not
>>>> working, I'm stuck with "No repository found" for all the bundles...
>>>
>>>> Laurent.
>>>
>>>> Laurent Marchal a écrit :
>>>>> Hello Christian,
>>>>>
>>>>> Thanks for the clarification, the error is that I used the
>>>>> site.xml with my top level feature inside, with the p2 publisher to
>>>>> generate the update site. So the product itself could not be updated.
>>>>>
>>>>> I understand better, and now when I make the update-site pointing
>>>>> directly to the repository generated by the build, my RCP app
>>>>> detect that an update is available for the product and all
>>>>> contained features.
>>>>>
>>>>> The only problem is when p2 wants to download the files, it says :
>>>>> "no repository found for ...."
>>>>>
>>>>> An error occurred while collecting items to be installed
>>>>> session context was:(profile=profile,
>>>>> phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect,
>>>>> operand=, action=).
>>>>> No repository found containing:
>>>>> osgi.bundle,com.sma.core,1.0.0.200907091056
>>>>> No repository found containing:
>>>>> osgi.bundle,com.sma.ui.administration,1.0.0.200907091056
>>>>> No repository found containing:
>>>>> osgi.bundle,com.sma.ui.administration.job,1.0.0.200907091056
>>>>>
>>>>>
>>>>> All the features and plugins are there, but I think there should be
>>>>> an URL somewhere in the content.xml/artifacts.xml that is pointing
>>>>> to local files, because it was generated by the build, instead of
>>>>> the remote URL of the update site.
>>>>>
>>>>> I don't know how to tell p2 to publish the repository as an update
>>>>> site ? should I mirror it ?
>>>>>
>>>>> Thanks.
>>>>> Laurent.
>>>>>
>>>>> Christian a écrit :
>>>>>> Laurent Marchal schrieb:
>>>>>>> Thanks a lot Andrew, your explanations are really helpful !
>>>>>>> In fact without your blog posts I could not get things working,
>>>>>>> for p2
>>>>>>> or the pde build.
>>>>>>>
>>>>>>> But for p2, I'm just discouraged. I have been working on updating
>>>>>>> my RCP
>>>>>>> application since eclipse 3.4, and it's been months I am trying
>>>>>>> without
>>>>>>> success. Each time, I have to spend days to learn and understand p2
>>>>>>> concepts, and it does not suffice to make it work. I understand
>>>>>>> that, as
>>>>>>> the new provisioning system, p2 needs to be able to make coffee
>>>>>>> and do
>>>>>>> anything possible but for me it's just too complicated to use and it
>>>>>>> drives me crazy.
>>>>>>>
>>>>>>> I don't want to criticize the work p2 developer made, It just
>>>>>>> don't fit
>>>>>>> my needs. p2 should be simple for easy things and complicated for
>>>>>>> complex tasks. It's just : complicated.
>>>>>>>
>>>>>>> I'm giving up p2, I will wait if someone find a decent solution
>>>>>>> for RCP applications.
>>>>>>>
>>>>>>> But once again, thanks for your help.
>>>>>>>
>>>>>>> Laurent Marchal.
>>>>>>
>>>>>> somehow you speak from my heart
>>>>>> p2 has a much to steep learning curve currently.
>>>>>> Some concepts are not as clear as they should be.
>>>>>> Deprecating old updatemanager for eclipse itself migth have been a
>>>>>> good idea... though may be one should have waited another Version
>>>>>> as for RCP apps its hard. Especially I want to reemphasize the
>>>>>> fact that I would have also been unable to get p2 to work in RCP
>>>>>> without Andrew's blog.
>>>>>>
>>>>>>
>>>>>>
>>>>>> About updateing RCP apps.
>>>>>>
>>>>>> It seems like there has been a concept change .
>>>>>> Before you updated the features and deployed them to the updatesite.
>>>>>>
>>>>>> Now you update the product and then use the repository that you
>>>>>> created while exporting as update site.
>>>>>> You no longer add the features directly to an update site (you
>>>>>> only do this if the features are not contained in the product at
>>>>>> least thats how it seemed to me) now you add the product itself.
>>>>>>
>>>>>> Adding just the features does not update the plugins in the
>>>>>> product but results in the problems you described.
>>>>>> (I know there was a lot of talk on the helpsites of the eclipse
>>>>>> project about the concept of Installable Units. Though this kind
>>>>>> of behaviour was not deducable from reading that for me.)
>>>>>>
>>>>>> Christian
>>>
>>>
>
>
|
|
|
| Re: [P2] Updates treated as conflicts [message #135531 is a reply to message #135115] |
Fri, 10 July 2009 19:33 |
| Eclipse User |
|
|
|
Originally posted by: fakemail.xyz.de
Laurent Marchal schrieb:
> I can install the RCP application directly from my update site using the
> p2 agent without any problems. It's just the update that is not working,
> I'm stuck with "No repository found" for all the bundles...
>
> Laurent.
>
Do you have that magical p2.inf file next to your product when exporting?
|
|
|
| Re: [P2] Updates treated as conflicts [message #135684 is a reply to message #135531] |
Thu, 16 July 2009 12:42 |
Laurent Marchal
Messages: 91
Registered: July 2009 |
Member |
|
|
Ok I found the solution :
I tried all the possibilities to find what was wrong : install with the
p2 agent, use the p2 installer, tried the p2 mirrorring... Everything
was working so the problem did not come from my "update site" repository.
The error in my RCP app was : "No repository found containing: some
bundles" which means no ARTIFACT repository found containing the
bundles. My p2.inf was like :
addRepository(type:0,enabled:true,name:Updates,location:http ${#58}//some.update.site);
After reading for the 10th time the documentation
http://wiki.eclipse.org/Equinox_p2_Touchpoint_Instructions I saw that
the "type" parameter indicates if it's a metadata repository or an
artifact repository. OK! I have only declared the metadata repository
not the artifact one in the p2.inf, so the artifact repository could
never be found !
Now the valid p2.inf is like :
addRepository(type:0,enabled:true,name:Updates,location:http ${#58}//some.update.site);
addRepository(type:1,enabled:true,name:Updates,location:http ${#58}//some.update.site);
and everything is working nicely !
Thanks everyone for your help.
Hope with time that p2 will be become simple for simple things.
Laurent Marchal.
Christian a écrit :
> Laurent Marchal schrieb:
>> I can install the RCP application directly from my update site using
>> the p2 agent without any problems. It's just the update that is not
>> working, I'm stuck with "No repository found" for all the bundles...
>>
>> Laurent.
>>
>
> Do you have that magical p2.inf file next to your product when exporting?
>
>
|
|
|
Goto Forum:
Current Time: Fri Dec 27 02:29:46 GMT 2024
Powered by FUDForum. Page generated in 0.04262 seconds |
] 
Search
Help
Register
Login
Home
