We are building an Eclipse RCP based application and would like to upgrade to the latest release of the spring-osgi integration bundles (Spring-DM). We are experiencing a particular problem with cyclical dependencies and I was wondering how the community would suggest moving forward.
Basically we are having the same problem as described in the following post: post id = 63250, title = "Classpath cycle" (it won't let me post a link to it until I have at least 5 posts). However, we are experiencing it with core and context instead of context and orm. Our dependencies look like this:
Our plugin -> org.springframework.bundle.osgi.core_1.1.2 -> org.springframework.bundle.spring.context_2.5.5 -> our plugin since it is the easiest way to depend on org.springframework.bundle.osgi.core_1.1.2.
In the post mentioned above, they simply hacked the manifest file to remove the dependency since it was optional. Now, whilst this method is not ideal since we would have to change it every time we upgrade to the latest bundles, I would be willing to do it if someone could confirm that the dependency cycle we have is optional and that this is a valid work-around.
Any ideas or thoughts?