On this post from 2015 https://groups.google.com/g/bndtools-dev/c/pKdZ2fQZ0KE/m/PZuWBD9HLvkJ you can read:
- We now faithfully use the build JAR file instead of the bin folder with version=latest. Version=project uses the bin folder directly. Using the JAR means that any extra packaged code will be visible in downstream projects.
- We probably need to watch upstream dependency’s bin folder if version=project. In practice, this generates a new compile for downstream projects, which should trigger the bnd build. However, there could be a possibility we do not pick up changes. Needs some further thought.
Could somebody elaborate about the impact of having version=project
vs. version=latest
on the -buildpath
in bnd.bnd
?
- When is the one or the other recommended for workspace-bundles?
- Does this e.g. have an impact on Eclipse build performance?
Summary
One thing we noticed that for bundles which export some packages of “wrapped” external libs, we need to use version=latest
, because otherwise those exported packages are not visible, because of…
“Using the JAR means that any extra packaged code will be visible in downstream projects”
But for other pure-workspace bundles version=project
works fine.