I don’t undestand why openhab launch such slow when we have the openhab-core source inside eclipse.
More specifically, I don’t undestand what happens during the phase “Performing final launch validation …” when you launch the app.bndrun debug configuration.
As far as I can see, in this phase, all build are finished, and if I understand, the bndtools just have to verify that all jar in features.xml are present and valid, and then launch the karaf runtime.
The matter is that under full eclipse with core source, this phase take around 1m30 to 2mn on my computer.
When I have only the distro with a few addon in my eclipse, the phase only take 3s-5s !
Do someone know if there is a way to speedup this phase, this is very annoying when you restart the runtime many time to debug change.
I am not quite sure, but bnd launch is somewhat separate from karaf. It launches openHAB core based on runfile which lists all necessary bundles. While it may contain karaf bundles, it is completely different way to spin a thing.
Some of validation is simply making sure that all inner packages are resolved. However, under the hood, there is an abstract concept of requirements and capabilities which is checking a lot more. That part can take a lot of time, especially if you have complete runtime with all needed dependencies.
Have you observed any high resource utilisation when task in question is being performed?
Disk access is for sure happening, because modules and their metadata are being read. I am not sure if it is cached at Eclipse or Bnd level, since contents of your .m2 repository might be changed from outside of IDE thought i.e. command line call to mvn.
