|Re: [p2-dev] Product publishing and product update|
That's certainly one way of looking at it. Another is that by using ranges (i.e. requires), you create flexible and agile entities that can coexist in several different combinations while trusting the framework (i.e. p2 and OSGi) to provide the necessary stability. I.e. you get out of the "dll hell" problem.
I strongly caution people *against* making container features that use requires rather than includes to get flexibility in updating products. This will lead to non-determinisim and unmaintainable end-user installs unless you carefully manage the repos available to your end users.
Regards, Thomas Hallgren