Bug 1198298 - The hibernate.search.engine module needs to be refactored
Summary: The hibernate.search.engine module needs to be refactored
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: EAP modules
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: 6.5.0
Assignee: Gustavo Fernandes
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: jdg65-Beta-Blcokers
TreeView+ depends on / blocked
 
Reported: 2015-03-03 18:15 UTC by Alan Field
Modified: 2015-06-23 12:25 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-23 12:25:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alan Field 2015-03-03 18:15:27 UTC
Description of problem:

From an email exchange with Sanne:

> In the DR2 build of JDG 6.5, I see the following search related modules
> defined:
> 
> org.hibernate.search.engine which has the following resources:
>     <resources>
>         <resource-root path="avro-1.7.5.redhat-2.jar"/>
>         <resource-root
>         path="hibernate-search-engine-4.6.0.Final-redhat-1.jar"/>
>         <resource-root
>         path="hibernate-search-infinispan-4.6.0.Final-redhat-1.jar"/>
>         <resource-root
>         path="hibernate-search-analyzers-4.6.0.Final-redhat-1.jar"/>
>         <!-- Insert resources here -->
>     </resources>

This module needs to be split up in more fine grained:
 - Avro already exists as a module within EAP, however not all of them so you might want to keep it here if this is meant for Infinispan Query to work on older versions of EAP (I'm not sure how far back we support that)
 - hibernate-search-infinispan definitely needs to be in a separate module.

The correct module name and packaging was decided here:
 https://github.com/infinispan/jdg/pull/291

We implemented this module structure in Hibernate Search, the code which builds that module though needs to be migrated into Infinispan upstream && into JDG 6.5


Note You need to log in before you can comment on or make changes to this bug.