Mike Kobler

The camel-karaf catalog does exist in my local repository. In the file idea.log I get the following warning: 2022-10-09 13:30:15,062 [5374216] WARN - #c.g.c.i.s.CamelMavenVersionManager - Could not load the catalog...

Same problem with a more recent version: 2022-10-09 15:20:02,842 [11961996] FINE - #c.g.c.i.s.CamelMavenVersionManager - java.lang.RuntimeException: Error grabbing Grapes -- [unresolved dependency: org.apache.camel#camel-catalog;3.14.5: not found] at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:455) at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:625) at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:592)...

Thanks for the tip with grapeConfig.xml. I was able to solve the issue by adding the repos to the XML and selecting the runtime provider "Auto detect". However, when I...

[idea.log](https://github.com/camel-tooling/camel-idea-plugin/files/9983963/idea.log)

Yes, same problem with with your linked project (version 3.7.0) as soon as I switch the runtime provider in the plugin settings to "Karaf". Error: "Camel IDEA plugin cannot download...

Same for Quarkus and Spring Boot. Only Default and Auto detect (Default) seems to work.

Same problem. With version 3.18 even the Default runtime can't be downloaded.

After a restart of IDEA, the download now seems to work for the "Default" runtime with Camel 3.18.0. No idea what caused the problem before. Sorry for the circumstances.

I created the commits on the dev branch and then merged them to the master branch. Afterwards I started the pipeline for the master branch which created the Git tag...

That seems to work. But this was only a test case. Normally we use gitflow workflow and therefore never merge the master branch back to dev. The release branch will...