Virgo tooling : Bundle dependencies broken once changed MANIFEST.MF of a installed bundle [message #985508] |
Thu, 15 November 2012 13:02 |
Jay Huang Messages: 20 Registered: February 2012 |
Junior Member |
|
|
Hi all, I am using VTS 3.6.M2 and snapshot eclipse tooling on Elcipse 3.7 Indigo + Java 7, EVERYTIME I change the bundle dependency in MANIFEST.MF (add/remove/modify a import bundle/package) of an installed bundle in a running virgo server through the tooling, some of the dependencies(not fixed ones, everytime is different) in the MANIFEST.MF become unresolved, then I have to stop the server, make some change to MANIFEST.MF -> change it back -> save, then the dependencies become normal again. Sometimes it breaks other unrelated bundles as well. A similar problem also occurs when attaching a source jar to a .class file from a running bundle. It seems to me that in a running virgo, everything that makes the tooling touches the Virgo's repository index will break. Sometime the bundle dependencies are broken in a newly started eclipse, trigger a MANIFEST.MF save will fix it.
The previous versions of VTS and tooling also had the same problem.
Has anyone else had the same problem? As I have been experiencing this for a long time but I haven't seen it raised. Is this a known issue? is there a workaround?
Cheers.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03200 seconds