What about toolinggtk.linux.x86org.eclipse.equinox.ds IU? Does it make sense for it to require any bundle? I realize this requirement will be satisfied by the host bundle not other bundles will be brought into solution, but is this just minor publisher sloppiness or there is more to it?
-- Regards, Igor On 12-08-09 8:31 AM, Pascal Rapicault wrote:
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. HTH Pascal 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 <required namespace='org.eclipse.equinox.p2.eclipse.type' name='bundle' range='[1.0.0,2.0.0)' greedy='false'/> Did I get this right? What is the reason behind these? -- Regards, Igor _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
