FWIW I use IntelliJ and merely open the gradle project naturally. I
have never run "gradlew idea" nor know what the point of that is.
On Mon, Jul 15, 2024 at 12:01 PM Ishan Chattopadhyaya
wrote:
>
> Thanks Jason and Christos,
> Apologies, I meant "./gradlew idea" instead of "./gradlew main". It
Thanks Jason and Christos,
Apologies, I meant "./gradlew idea" instead of "./gradlew main". It
generates an IntelliJ project that didn't load for me.
I'll try to reproduce this on another machine and record a screencast for
it, to help further debugging.
Thanks and regards,
Ishan
On Mon, 15 Jul 20
> Cannot resolve symbol CollectionsApi, ListCollectionsResponse.
+1 to what Christos said.
In short - 'CollectionsApi' and 'ListCollectionsResponse' are both
Java classes that we generate from our OAS. That generation is setup
in gradle to always happen prior to compiling "solr-solrj" (which of
Hey Ishan, I'm sorry to hear that. The test uses a generated class to
verify the bug fix, since the issue occurs in a template fro class
generation.
The error you sent points to one of generated classes that I used
(CollectionsApi) and that is also in SolrJ module. Since it is a generated
class, i
I removed the ApiMustacheTemplateTests.java temporarily, and all errors
went away.
However, tried running tests, and ran into this:
BasicFunctionalityTest.java:
java.lang.RuntimeException:
org.apache.solr.core.SolrCoreInitializationException: SolrCore
'collection1' is not available due to init fai
