Browse Repos empty when index changes

[cschneider]

I have a very frequent problem in bndtools 3.5.0.REL-20170929-190052-ga0d7a6b on macos.

In my project I generate the index from a pom using the bnd-indexer-maven-pugin. In the same maven project I have a bndrun file that refers to this index.

Now the problem is that in many cases the Browse Repos view is empty and I need to close and reopen the bndrun editor to get the repo view again.

My assumption is that whenever any file in the project changes the index is regenerated (which is a bit eager but not completely incorrect). Now whenever the index changes it seems that the Browse Repos view is emptied and not usable from this point on.

The most obvious case when this happens is when I first delete the runbundles, then I press revolve and then save the bndrun file. The issue always happens in this case .. which makes using bndtools a real pain at the moment.

Another simple way to reproduce is to open the bndrun editor. The repo is shown. Then open the pom, add a space soemewhere, save and switch back to the editor. The repo view is now empty.

So I think the correct behaviour in bndtools is that the bndrun editor should be able to cope with changes in the index without needing a restart.
Additionally it might be a good idea that the bnd-indexer-maven-plugin only reacts on changes of the pom.. not of any file. (This is only an assumption though. I have no hard proof that the indexer awlays runs).

[cschneider]

You can try with this project and bndrun file: https://github.com/apache/karaf-reactive-components/blob/master/rcomp-app/rcomp-example.bndrun

[cschneider]

Btw. I just checked with the newest snapshot of bndtools today and the issue is still there.

[bjhargrave]

@timothyjward Can you look at this?

[cschneider]

I just found how to work around this .. or maybe I simply did it wrong.
When looking at the enroute microservice example I found that there the issue does not show.
So I checked what is different there.
This is what I used:
-standalone: ${.}/target/index.xml
This what the microservice example uses:
index: target/index.xml;name="rest-app"
-standalone: ${index}

When I switch to this config the problem is gone.