Community
Participate
Working Groups
Currently the OSGi integration bundle has the version 1.0.0.qualifier but it's already included in our build. I think we should adopt the current RAP version number 1.5.0 to avoid confusion.
-1 As I consider the unification of bundle versions a bad practice, I would prefer to close this issue as INVALID. But probably I do not find much Allies on this in the team, so I won't start a war over it :-)
Regardless if this is a good or bad approach, we are doing this with all RAP bundles for a long time now. I think the OSGi Integration should not be an exception.
Hm - as I told you before, I will not start a war over this but I would prefer to change the practice used with all of the RAP bundles. The current approach leads to new bundle version numbers for each bundle in a release train regardless whether the bundle actually has changes or not. And for the rwt-osgi integration bundle it is the first version, not 1.5 ...
(In reply to comment #3) > Hm - as I told you before, I will not start a war over this but I would prefer > to change the practice used with all of the RAP bundles. The current approach > leads to new bundle version numbers for each bundle in a release train > regardless whether the bundle actually has changes or not. And for the rwt-osgi > integration bundle it is the first version, not 1.5 ... I really agree with Frank, but in my mind it not worth changing the practice for one bundle at this point in time. However, if in the future we decide to version each bundle, it would be an extra burden to us to enforce and track. The real question is, what is the cost benefit of such a change. Is the gain worth the extra burden, etc. And also, is there a convention across the community for this? To me the canonical case in point is the use of RWT independent of RAP. To me it makes a lot of sense that RWT should be versioned differently.
Apparently, Rüdiger already changed the version to 1.5.0 in Sep 2011, probably without noticing this discussion. Since this version has been published in milestone builds already, we can't go back anymore. So I'm closing it as "fixed". I'm also not happy with our practice of changing the version number regardless of changes and I've opened bug 378646 for this issue.
