I have a maven project with couple of modules.
When I open two projects (modules) in Eclipse, eclipse starts "updating bundle classpath" for the projects, switching back and forth, eating CPU cycles and growing in memory.
If I disable the Spring OSGI nature, the message goes away. Closing one of the projects also makes the problem go away.
I'm going to attach a mavenized version of the spring-travel example which shows this problem.
Import the 'search' project, then import the 'webapp' project. That's enough to cause this problem.