[jdf-dev] JBoss Modules dependency vs pain POM dependency + exclusions

The Hibernate Search enabled version of TicketMonster relies on Hibernate Search 4.3 which itself has a dependency on Hibernate ORM included in WildFly and JBoss EAP. My first approach was to ask the user to add the Hibernate Search JBoss Module manually into their EAP / WildFly distribution and have it referenced in jboss-deployment-structure.xml. I also had to put Hibernate Search in my POM as provided because the BOM references an older version of Hibernate Search. To avoid the manual step, I tried to list Hibernate Search explicitly in the POM as regular scope and no longer use jboss-deployment-structure.xml. But then I have to play with exclusions which is not too nice either. Which approach is better suited for TicketMonster? And is there a better way? Here is the commit that moves from a module dependency to plain pom.xml https://github.com/emmanuelbernard/ticket-monster/commit/9da10a15921367d0... Emmanuel