I’d like to comment on what my goal is. I’d like to have a bunch of Karaf instances running in a cluster watching the development repo for new -SNAPSHOT bundles and updating the bundle as newer snapshot is available. I’m currently out of ideas. It seems that since the bundle is installed it is cached in local repo. And there’s no way at all to update this bundle because it is always present in local repository and the dev repo is never checked.
> On 2 Nov 2023, at 16:01, Pavel Perikov <[email protected]> wrote: > > Hi everybody. > > I’m using apache karaf-4.4.4. > > In clean configuration I made a single modification to > > org.ops4j.pax.url.mvn.repositories= \ > http://beelink:4000/snapshots@id=perikov@snapshots@noreleases, \ > > to add my own repository. > > Then I install the bundle org.name.0.1.0-SNAPSHOT from this repository. > > It seems like the bundle immediately gets cached to local ~/.m2 repo and > there’s no way to get newer snapshot. > > Neither bundle:update nor bundle:watch nor bundle:uninstall/bundle:install > again do not work (they use local repository, getting the old version). > > The only way to go is to delete the bundle from the local repo. > > Is there a way to get the correct behaviour (preferably the bundle should get > updated via bundle:watch)? > > Best regards, > Pavel >
