Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Populated wrong Lucene libraries

Description

Hi,

When I add Hibernate search 6.0.7.Final to an EAR project deployed on JBoss EAP 7.3 using Maven, Hibernate search populated old lucene libraries. There are old lucene libraries such as lucene-core-5.5.5.redhat-2.jar in lib/ directory of deployed EAR file.
I am not sure if this is a bug due to Hibernate Search or wrong settings.

Thanks,
Ben

Activity

Show:

Yoann RodièreOctober 27, 2021 at 7:30 AM

Hibernate Search 6 definitely doesn't depend on Lucene 5.5. That's not your problem. None of our tests would work if that was the case, and the build time checks (dependency convergence) we have in Hibernate Search would fail.

I suggest you check your own dependencies for references to Lucene 5.5 or Hibernate Search 5, which would indeed bring in Lucene 5.5 as a transitive dependency.

Also, check that WildFly isn't adding Hibernate Search 5 or Lucene 5.5 to your application; that's possible, since WildFly currently ships with Hibernate Search 5 and Lucene 5.5. If it's the case, I suppose you will have to go to the WildFly community for a solution.

I you need more help related to Hibernate Search, please use the appropriate channels instead of bug reports.

I'll close this ticket.

Rejected

Details

Assignee

Reporter

Affects versions

Priority

Created October 26, 2021 at 4:09 PM
Updated October 27, 2021 at 7:30 AM
Resolved October 27, 2021 at 7:30 AM