In the current bndtools SNAPSHOT there is an experimental feature which can save you lots of time when you save a java file.
The new Rebuild Trigger policy setting helps prevent unnecessary cascade rebuilds in Eclipse. With Optimized mode enabled, downstream projects rebuild only when the exported API of a dependency actually changes—not for every implementation-only edit.
Less waiting after every save, especially in larger bnd workspaces. It will be released with next bnd / bndtools 7.5.
Install bndtools SNAPSHOT: GitHub - bndtools/bnd: Bnd/Bndtools. Tooling to build OSGi bundles including Eclipse, Maven, and Gradle plugins. · GitHub
Docs: Bndtools Rebuild Trigger Policy Plugin | bnd
For me this solves a long time annoyance in bndtools compared to PDE Build which did not have the rebuild cascade problem because it can re-compile and replace single classes. In bnd this is more tricky. To be fair: there is a reason bnd works the way it works and it is also a good thing (build fidelity).
But a note of warning: The way this new feature works is kind of a trick (see limitations). It trades speed for 100% correctness, as there are cases where the feature does not work well. In case of doubt: don’t use the feature or do a manual clean workspace rebuild, if you have the feeling something is off and not rebuilding properly.