Hi, I tend to agree with Carsten on this one - having per-package OSGi version numbers makes sense, but without tools to manage that the risk of making a mess is high.
I would be +1 for having per-package version numbers if there was a tool to compute/enforce those numbers: using svn to compare code between bundle releases would let us know when a package version number needs to change - that doesn't seem too complicated, but we don't have such a tool ;-) Right now I'm for continuing to have bundle version == package version. That's a bit of a waste when only one package of a bundle actually changes between bundle releases, but if we find that happening too often we might want to just split that bundle into multiple bundles. -Bertrand
