Tried that, but many things can not get resolved that way in my case.

I am having some problems using elasticsearch-rest-high-level-client dependency in my project.According to Elasticsearch documentation only this should be included:<dependency>  <groupId>org.elasticsearch.client</groupId>  <artifactId>elasticsearch-rest-high-level-client</artifactId>  <version>7.4.0...

So my guess was right, transitive dependencies were not included altho Transitive>true</Embed-Transitive> exists.The following is necessary when running elasticsearch as search engine on AEM the problem:<!-- Elasticsearch -->  <dependency>       <groupId>org.elasticsearch.client</groupId>       <art...

Jackson dependencies are part of OSGi and should not be added as embed dependency. Please, correct me if I am wrong.I had a similar problem and figure out that there is already imported jackson dependency in intelliJ and I was overriding it with added jackson version.Please check External Dependenci...

Thank you for the effort, but it does not work in my case. Forbidding importing of packages that I am going to use should not fix the issue.I can not add an "elasticsearch" artifactId in <Embed-Dependency> because then build fails.Can you please try to clone my repo and try to make your changes, bec...

If I do it this way:<plugin>  <groupId>org.apache.felix</groupId>  <artifactId>maven-bundle-plugin</artifactId>  <extensions>true</extensions>  <executions>  <execution>  <id>bundle-manifest</id>  <phase>process-classes</phase>  <goals>  <goal>manifest</goal>  </goals>  </execution>  </executions>  ...

I am trying to use Java High Level Rest Client in Adobe Experience Manager to finish project of comparisson between Lucene, Solr and Elasticsearch search engines.I am having some problems with dependencies that I don't understand so any info on this would be valid.Here is the code:Dependencies in th...

Does that mean that without these properties defined, these indexes would be indexed?if the structure is like this:- lucene     - aggregates (nt:file)     - indexRules          - nt:base               - properties (nothing inside)Would then everything that is (or extends) nt:file be indexed (every s...

Per Lucene documentation, the following is definition of Indexing Rules on oak indexes inside AEM:Indexing rules defines which types of node and properties are indexed. An index configuration can define one or more indexingRules for different nodeTypes.However, when I check on indexes created in We ...

It makes sense, I just thought it should run "infinity cost" if there is no cost lower than that. I will mark your question as correct. Thank you