Hi
I am experiencing very annoying behavior when developing osgi bundles within eclipse when using SpringSource Eclipse Tooling. I have a bundle deployed into dm Server running from inside Eclipse. When I make a change to MANIFEST.MF and save it, this bundle gets automatically redeployed as expected.
At this point, I see this in console output:
However, when the change I make causes bundle to fail during the deployment because of the missing Import-Package statement which ultimately causes java.lang.ClassNotFoundException, I get this output:Code:<SPDE0010I> Deployment of 'org.xyz' version '1' completed.
Trying to fix it, I get this behavior. I go and change the manifest by adding the missing Import-Package statement and re-save. Bundle gets redeployed automatically again, this time successfully, but the name and version of the deployed bundle is incorrect. This is what I see in console output:Code:<SPDE0011E> Deployment of 'org.xyz' version '1' failed.
Please note that '.jar' is added and version changes from 1 to 0. This also causes that other bundles relying on this bundle won't get deployed as org.xyz_1.0.0 is not available.Code:<SPDE0010I> Deployment of 'org.xyz.jar' version '0' completed.
As a workaround I found out this sequence of steps:
1. I go to manifest editor Runtime tab
2. Click on Properties for an exported package.
3. Remove any version for that Export-Package statement.
4. Click OK
5. Click on Properties for an exported package again.
6. Add 1.0.0 version for that Export-Package statement.
7. Click OK
8. Save
At this point, bundle gets redeployed automatically again, but this time correctly as:
Any idea what might be wrong?Code:<SPDE0010I> Deployment of 'org.xyz' version '1' completed.


