|Re: [cross-project-issues-dev] dependencies, build and P2|
Am 18.12.2010 12:00, schrieb Thomas Hallgren:
On 2010-12-18 11:46, Eike Stepper wrote:Hi Thomas, I like this idea very much, although I'm not sure if I fully understand all implications. Would that mean that, for ourselves, we work around a severe issue (the issue that a feature.xml can not include ranges), but still leave our end consumers with that very issue?The setup would ensure that everything that is produced would be consistent beyond the scope of your own build. The lack of version ranges in features "includes" is another issue altogether. The recommendation is that you use feature "requirements" for all things that you don't produce (and hence ranges) and "includes" for the things that you produce. The requirements does allow ranges and they should not be tighter than necessary to ensure that your feature can play well with others.
Oh, I seem to understand now. That would enable us to remove any mention of Orbit bundles/features altogether from our own feature.xmls because the release train repo would include them and our bundle manifest dependencies would be used by p2. Great! Cheers /Eike ---- http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper
Back to the top