Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » P2 update for RCP product fails
P2 update for RCP product fails [message #1722710] Mon, 08 February 2016 13:22 Go to next message
Axel Guckelsberger is currently offline Axel GuckelsbergerFriend
Messages: 336
Registered: July 2009
Senior Member
Hi all,

I've facing a problem with the update functionality and hope you can
give me an advise.

Here is the setup:

1. The product is based on features.
2. The product contains two features: the product feature and p2.core.
3. The product feature contains all other features, the branding plug-in
and the update plug-in.

Also in the "available software" dialog the product feature shows the
"new" icon instead of the "update available" icon.

The error message I receive is
   Your original request has been modified.
     Product is already installed, so an update will be performed instead.

  Only one of the following can be installed at once:
     Branding Plug-in 1.0.0.201602081058
     Branding Plug-in 1.0.0.201602081040

   Cannot satisfy dependency:
     From: Product 1.0.0.qualifier
     To: product.feature [1.0.0.201602081041-7yC8EC9cD-Cn-BgODOkEYMoCqVOD]

   Cannot satisfy dependency:
     From: product.feature 1.0.0.201602081041-7yC8EC9cD-Cn-BgODOkEYMoCqVOD
     To: product.branding [1.0.0.201602081040]

   Cannot satisfy dependency:
     From: product.feature 1.0.0.201602081059-7yC8EC9cD-Cn-BgODOkEYMoCreOD
     To: product.branding [1.0.0.201602081058]



The "about > installed software" dialog shows the produt as root node
which contains the product feature as a child. This is probably causing
the problem because only root nodes can be updated, right?

I think to update the feature independently from the product definition
I would need to mark it as installMode="root" (which seems to be a Tycho
concept). Or I need to have the product itself installable at the update
site, too.

So I have the following questions:
1. Why is the product qualifier (specified in the product definition
file) not replaced?
2. Why doesn't the product itself update from the p2 site (which
includes the product executables in the "binary" directory though)?
3. What do I need to change in my setup to fix the conflict shown above
(making it work somehow)?
4. Do I need to switch to Tycho for that?

Thank you very much!

Axel

[Updated on: Mon, 08 February 2016 13:26]

Report message to a moderator

Re: P2 update for RCP product fails [message #1723956 is a reply to message #1722710] Fri, 19 February 2016 09:32 Go to previous messageGo to next message
Axel Guckelsberger is currently offline Axel GuckelsbergerFriend
Messages: 336
Registered: July 2009
Senior Member
Hi,

do you have any idea how to proceed with this issue?

Axel


Am 08.02.2016 um 14:22 schrieb Axel Guckelsberger:
> Hi all,
>
> I've facing a problem with the update functionality and hope you can
> give me an advise.
>
> Here is the setup:
>
> 1. The product is based on features.
> 2. The product contains two features: the product feature and p2.core.
> 3. The product feature contains all other features, the branding plug-in
> and the update plug-in.
>
> Also in the "available software" dialog the product feature shows the
> "new" icon instead of the "update available" icon.
>
> The error message I receive is
> Your original request has been modified.
>
> Product is already installed, so an update will be performed instead.
>
> Only one of the following can be installed at once:
>
> Branding Plug-in 1.0.0.201602081058
> Branding Plug-in 1.0.0.201602081040
> Cannot satisfy dependency:
>
> From: Product 1.0.0.qualifier
> To: product.feature [1.0.0.201602081041-7yC8EC9cD-Cn-BgODOkEYMoCqVOD]
>
> Cannot satisfy dependency:
>
> From: product.feature 1.0.0.201602081041-7yC8EC9cD-Cn-BgODOkEYMoCqVOD
>
> To: product.branding [1.0.0.201602081040]
>
> Cannot satisfy dependency:
>
> From: product.feature 1.0.0.201602081059-7yC8EC9cD-Cn-BgODOkEYMoCreOD
>
> To: product.branding [1.0.0.201602081058]
>
>
> The "about > installed software" dialog shows the produt as root node
> which contains the product feature as a child. This is probably causing
> the problem because only root nodes can be updated, right?
>
> I think to update the feature independently from the product definition
> I would need to mark it as installMode="root" (which seems to be a Tycho
> concept). Or I need to have the product itself installable at the update
> site, too.
>
> So I have the following questions:
> 1. Why is the product qualifier (specified in the product definition
> file) not replaced?
> 2. Why doesn't the product itself update from the p2 site (which
> includes the product executables in the "binary" directory though)?
> 3. What do I need to change in my setup to fix the conflict shown above
> (making it work somehow)?
> 4. Do I need to switch to Tycho for that?
>
> Thank you very much!
>
> Axel
Re: P2 update for RCP product fails [message #1724224 is a reply to message #1722710] Mon, 22 February 2016 11:13 Go to previous messageGo to next message
Lorenzo Bettini is currently offline Lorenzo BettiniFriend
Messages: 1750
Registered: July 2009
Location: Firenze, Italy
Senior Member
On 08/02/2016 14:22, Axel Guckelsberger wrote:
> Hi all,
>
> I've facing a problem with the update functionality and hope you can
> give me an advise.
>
> Here is the setup:
>
> 1. The product is based on features.
> 2. The product contains two features: the product feature and p2.core.
> 3. The product feature contains all other features, the branding plug-in
> and the update plug-in.
>
> Also in the "available software" dialog the product feature shows the
> "new" icon instead of the "update available" icon.
>
> The error message I receive is
> Your original request has been modified.
>
> Product is already installed, so an update will be performed instead.
>
> Only one of the following can be installed at once:
>
> Branding Plug-in 1.0.0.201602081058
> Branding Plug-in 1.0.0.201602081040
> Cannot satisfy dependency:
>
> From: Product 1.0.0.qualifier
> To: product.feature [1.0.0.201602081041-7yC8EC9cD-Cn-BgODOkEYMoCqVOD]
>
> Cannot satisfy dependency:
>
> From: product.feature 1.0.0.201602081041-7yC8EC9cD-Cn-BgODOkEYMoCqVOD
>
> To: product.branding [1.0.0.201602081040]
>
> Cannot satisfy dependency:
>
> From: product.feature 1.0.0.201602081059-7yC8EC9cD-Cn-BgODOkEYMoCreOD
>
> To: product.branding [1.0.0.201602081058]
>
>
> The "about > installed software" dialog shows the produt as root node
> which contains the product feature as a child. This is probably causing
> the problem because only root nodes can be updated, right?
>
> I think to update the feature independently from the product definition
> I would need to mark it as installMode="root" (which seems to be a Tycho
> concept). Or I need to have the product itself installable at the update
> site, too.
>
> So I have the following questions:
> 1. Why is the product qualifier (specified in the product definition
> file) not replaced?
> 2. Why doesn't the product itself update from the p2 site (which
> includes the product executables in the "binary" directory though)?
> 3. What do I need to change in my setup to fix the conflict shown above
> (making it work somehow)?
> 4. Do I need to switch to Tycho for that?
>
> Thank you very much!
>
> Axel

Hi Axel

I think that you can still update features independently from the
product definition as long as the feature of the product *depends* on
such features, and not *includes* such features. In fact, including a
feature results in a exact version range for that feature, while when
you depend on a feature (or plug-in) you can 'relax' the dependency
version range (and you can specify no range at all).

However, note that the features and bundles your feature depends on,
will NOT be included in the generated p2 repository. This means that
you may have to produce different repositories yourself (e.g., one for
the product's feature and one for the dependency features). You can
then (b3)-aggregate them or create a composite update site.

Hope this helps
cheers
Lorenzo

--
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Re: P2 update for RCP product fails [message #1725091 is a reply to message #1724224] Mon, 29 February 2016 16:50 Go to previous message
Axel Guckelsberger is currently offline Axel GuckelsbergerFriend
Messages: 336
Registered: July 2009
Senior Member
Hi all,

I finally found the solution :-)

The actual problem was that the updated product was never recognised,
because the product's qualifier has not been dynamically replaced.
1.0.0.qualifier was always installed already, so no upgrade was found.

The solution is here:
https://www.eclipse.org/forums/index.php?t=msg&th=155943&goto=491414&#msg_491414

While searching in the newsgroup I've found several posts from Thomas
where he explained that. But it is still not very obvious and looks like
insider knowledge. Thus, please add this to the official documentation.

HTH,
Axel


>
> Hi Axel
>
> I think that you can still update features independently from the
> product definition as long as the feature of the product *depends* on
> such features, and not *includes* such features. In fact, including a
> feature results in a exact version range for that feature, while when
> you depend on a feature (or plug-in) you can 'relax' the dependency
> version range (and you can specify no range at all).
>
> However, note that the features and bundles your feature depends on,
> will NOT be included in the generated p2 repository. This means that
> you may have to produce different repositories yourself (e.g., one for
> the product's feature and one for the dependency features). You can
> then (b3)-aggregate them or create a composite update site.
>
> Hope this helps
> cheers
> Lorenzo
>
Previous Topic:Buckminster adds version ranges to my plugins when building p2 site
Next Topic:Target platform not materializing
Goto Forum:
  


Current Time: Mon May 21 11:05:35 GMT 2018

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

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

Back to the top