[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] tooling... IU requirements
- From: Pascal Rapicault <pascal@xxxxxxxxxxxxx>
- Date: Thu, 9 Aug 2012 14:31:57 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=rapicault.net; h=content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; q=dns; s= rapicault.net; b=li8EX+Nay3AQSZ7ziw7InKCwjztTsBqCKtncCbT30gUfbMv XohDGM/b8pTNN+3x9fBUBqo7SA2eaxLnX2fjcbd12HxqUOlTosn8AQ7s8OYuzJL+ j+z/g2GCcjLIsk+xlH1yMFRe6JijXVZ5SPuAi5N1QfvM+94pETan8CJwIgv8=
Yes this is correct. The goal of such IUs is to apply a common configuration to all the bundles.
For example in Eclipse every bundles but a few need to be started at start level 4. Since nothing happens for free in p2, there needs to be a configuration unit (an IUFragment) to delivers this information to every bundle. To avoid the creation of a plethora of CU (one per IU that delivers a bundle) it is much more maintainable to have one CU that attaches to multiple IUs. An example of such IU is tooling.osgi.bundle.default.
On 2012-08-09, at 1:54 PM, Igor Fedorenko wrote:
> I've noticed that many/all toolingBLAH IUs have a requirement that appear to be satisfied by any bundle
> Did I get this right? What is the reason behind these?
> p2-dev mailing list