I really appreciate the fact that nebula is now an eclipse project and i was really happy as i saw the link to the update site on your homepage
But now i have an annoying problem with an old version of the composite table plugin..
As i added this feature the first time to the target platform i got the version in the attachment. It´s only slightly different to the latest version on the update site (hxxp://download.eclipse.org/technology/nebula/snapshot/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar)
More or less it´s just that the package is called 'org.eclipse.swt.nebula' instead of 'org.eclipse.nebula' ..
That bad thing now was, that my eclipse installation kept downloading this 'old' version when my co-workers (they resolved the target definition the first time a few days later..) already got the 'new' version ..
The solution was to re-install eclipse - deleting the .bundle_pool / workspace didn´t help .. Now only our build server keeps downloading this 'old' file :-/
Can you think of a possible reason for this behavior? It´s not our proxy server and i deleted all local repos / caches i could think of ..
The issue may come from the fact that the version is 1.0.0 and not
1.0.0.[qualifier]. Then when installing, p2 thinks you are up-to-date
with your 1.0.0.
A good way to get it working could be to first uninstall you previous
version of the bundle, and then install the more recent one.
To get it fixed in Nebula, please open a bug to request plugins to use a
4-segments versioning with a qualifier to avoid this issue.
On 25/01/2012 12:21, Tilman Reinhardt wrote:
> Thanks for the reply!
> Actually i think the problem is that both plugins are releases (without
> a qualifier) with the same version..
A release could/should have a qualifier too - that's the main point
where OSGi conventions differ from Maven conventions. P2 *requires*
qualifier to work well with updates and so on.
Switching to 1.0.0.qualifier
> wouldn´t help in this case, right?
Yes, it would. A better approach would be that the target plugin would
handle well versioning and move to 1.1.0, but that's sometimes too
difficult to maintain, so having a qualifier with build date almost
ensures you you have the latest release.