[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Shared installs and our EPP Packages
- From: Francis Upton <francisu@xxxxxxxx>
- Date: Thu, 12 Aug 2010 09:26:18 -0700
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=OF5b8QAFvHVLpk35JVTz7VOWRNpr6cvRf4Mnc2/Y89/Ol/5lnMkNSMnW5NBcr0l0Or WHBUNdcuHUP1J67KT8HU0j46wuMexWD6t6GdJCO4haF4dWmuWaOCjsDjYEEfQKTk7Tja tg1EKJd5m2K8ZbNu8gYDNDXgQqXTzoy4C/1ws=
* When we run in a shared install scenario, we create a bundles.info
file from the p2 profile. When Eclipse is launched, our generated bundles.info
file is checked against the shared one, and if any inconsistencies are found, we ignore ours and use the shared one. However, the shared one is read only, and will never contain the additional bundles.
I think there might be two parts of this problem, the more serious part is "if any inconsisencies are found". I'm not sure what you mean by that, but the problem is that the installation silently and completely succeeds from a user point of view and even shows the software installed, except that none of the plugins are actually there. This should never happen no matter what, at least the installation should fail. And then the second part of course is to make it work (which may be an issue with the packages and p2).