[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] P2 built product -- cannot update features contained within
- From: Brian de Alwis <briandealwis@xxxxxxxxx>
- Date: Wed, 18 May 2011 17:17:09 -0400
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=aH0v/9FEoZ9RDYjcewH/iZTlOc4ecQhSCdI+bAJNUKEDhcJvJH7E7pKP+47UleUrIX Z4PAaLXMWLZcs2HEL1Fi1DZvKZUC6BeAgCboJiFZJyCuHicR+Az5Q8tEfPOqPvRWWoZ3 vWC410E3jvLjsOvZ9EQdjddxhK/Vt5WXHrYL8=
Hi Eddie. See Andrew Niefer's blog post that demonstrates how to use a p2.inf file to specify feature dependencies with version ranges
On 18-May-2011, at 5:02 PM, Eddie Galvez wrote:
> (see also https://bugs.eclipse.org/bugs/show_bug.cgi?id=279659)
> We build a product. Product file has dependencies (no version specified, not
> even 0.0.0) on features, like "org.eclipse.team.svn".
> We do a PDE build using P2 of our product.
> The end result is a product that end-users cannot upgrade, in this case,
> org.eclipse.team.svn. They'll get the "Only one of the following can be
> installed at once"
> From bug 279659 I gather that:
> A reason is that something is marked âsingleton trueâ by default. But thereâs no control over this.
> I read suggestions of using installiu/uninstalliu director commands; I could not get those to work, but for now let me not focus on that.
> So, what can we do to help our end users? Itâs important for us to ship the SVN feature for convenience, but we definitely need end-users to be able to upgrade it!
> Thank you,
> p2-dev mailing list