> It is all about right version range in manifest. IMO it should be > open range with version from Indigo SR0. Now in most cases dev's > just use SR1 and when new dependency added pde adds it as open range > with lower version from SR1. > > Denis Agreed. Developers should be actively selecting the dependency version. It also helps to do a little research to see when a specific feature became available, as this may allow for backward compatibility (e.g. the SwitchYard plugins are fully compatible, although untested, with Eclipse JEE 3.6). It's probably too much to ask for existing dependencies, but as new dependencies are added, developers should actively select the version required. For existing dependencies, at a minimum, the "release" identifier should be replaced with a "0" unless a specific patch release is required. Best, Rob