Is it possible to revive camel-quarkus-solr now that camel-solr is back in camel 4

[Paul-Blanchaert]

Describe the feature here

As camel-solr was initially removed in early camel-4.x releases, the camel-quarkus-solr was removed from camel-quarkus via the commit Upgrade Camel to 4.0.0-M3.
In july this year, the camel-solr component found his way back in solr (jira ticket camel-solr: revive component and upgrade to the latest version).
Can we also revive the camel-quarkus-solr component?

[jamesnetherton]

We may run into issues with the Jetty version. solr-solrj depends on Jetty 10.x. However, this project aligns with Jetty 12.x.

org.apache.camel:camel-solr:jar:4.9.0-SNAPSHOT
+- org.apache.solr:solr-solrj:jar:9.7.0:compile
|  +- org.eclipse.jetty.http2:http2-client:jar:10.0.22:compile
|  |  \- org.eclipse.jetty:jetty-alpn-client:jar:10.0.22:compile
|  +- org.eclipse.jetty:jetty-http:jar:10.0.22:compile
|  +- org.eclipse.jetty:jetty-client:jar:10.0.22:runtime
|  +- org.eclipse.jetty:jetty-util:jar:10.0.22:compile
|  +- org.eclipse.jetty:jetty-io:jar:10.0.22:compile
|  \- org.eclipse.jetty:jetty-alpn-java-client:jar:10.0.22:runtime

It needs verifying but it may not work.

[Paul-Blanchaert]

Thanks for looking into this.
I was already preparing my "case files" to ask the camel project to refactor the solr component. We should be able reduce the scope of the camel-solr component and use a quite recent solrclient (HttpJdkSolrClient) that promises not to be dependent of jetty.
So I guess we should park this issue until we get the refactoring done on that side...
I'll refer to this issue when filing my "ticket" in camel.
To be continued...