Eclipse Community Forums: P2 » How to update after merging two features?

Help

Home

Home » Eclipse Projects » P2 » How to update after merging two features?

Show: Today's Messages :: Show Polls :: Message Navigator

How to update after merging two features? [message #1758122]

Thu, 23 March 2017 17:38

Julien HENRY

Messages: 8
Registered: July 2009

Junior Member

Hi guys,

My update site used to contain 2 features, and now I kept only one, putting all plugins in the remaining one.

Before:

  A.feature 1.0
     / a.plugin 1.0
  B.feature 1.0
     / b.plugin 1.0

After:

  A.feature 2.0
     / a.plugin 2.0
     / b.plugin 2.0

I would like to offer smooth update experience for the end users. Currently the update fail, saying that B.feature 1.0 depends on b.plugin 1.0 and so b.plugin 2.0 can't be installed at the same time.

I discovered the possibility to tune p2 behavior. So I tried to add a p2.inf file in the remaining feature, with:

update.matchExp=providedCapabilities.exists(pc | pc.namespace \=\= 'org.eclipse.equinox.p2.iu' && (pc.name \=\= 'B.feature' || pc.name \=\= 'A.feature' && pc.version < '$version$'))

But it doesn't change anything. I found many projects using this functionality to rename a single feature (A updated by B). Is it supported in my use case (A+B updated by A)?

Thanks

Report message to a moderator

Re: How to update after merging two features? [message #1758405 is a reply to message #1758122]

Tue, 28 March 2017 13:01

Brian de Alwis

Messages: 837
Registered: January 2012

Senior Member

I'm definitely not a p2ql expert, but I'd have expected the closing bracket around the pc.name checks, like:

(pc.name \=\= 'B.feature' || pc.name \=\= 'A.feature') && pc.version < '$version$'

If that doesn't work, then I think you'd best post this to the p2-dev list.

Brian.

Eclipse Platform committer. Ask me about Eclipse support, training, and consulting.

Report message to a moderator

Re: How to update after merging two features? [message #1758408 is a reply to message #1758405]

Tue, 28 March 2017 13:18

Julien HENRY

Messages: 8
Registered: July 2009

Junior Member

Hi Brian,

In fact, after spending hours on this topic, I discovered that the behavior depends if you are using "Check for update" or "Install new software" paths.

With the update.matchExp entry, "Check for update" scenario is more or less ok. It says that installation can't be done, and that other options will be calculated. After a (very) long time it finally suggest that A should be upgraded and B uninstalled. So the final result is acceptable, it is just slow and not user friendly IMHO.

"Install new software" fails with a cryptic dependency error, and not even proposing to uninstall the old feature.

So I will rely on documentation to help the migration...

Report message to a moderator

Previous Topic:	Impact of replacing artifacts from an update site
Next Topic:	Eclipse Installer by oomph (Eclipse Indigo 3.7)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Jun 18 14:37:27 GMT 2019

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter