[
https://issues.jboss.org/browse/ISPN-7448?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-7448:
---------------------------------------
Careful with de-duplications, there are at least 3 version of Hibernate ORM being used,
and since each of them is in a different context they don't necessarily have to be
aligned.
- as dependency of the {{JpaStore}} -> this would be the ORM version we
"support" integration with
- the one included in WildFly -> we happen to run some integration tests on WildFly,
in this case test will need to keep in mind they are using the version as shipped with the
WildFly version of the day
- for integration tests with Hibernate Search & Hibernate ORM -> this is to test
the Infinispan / Lucene Directory and is meant to be compatible with the WildFly version
we'd target for "Infinispan Embedded usage within AS"
On a typical stable release they should probably be aligned, but since WildFly depends on
Infinispan we need to be able to release intermediary versions in which these three do not
align.
Not sure which one should be listed in the BOM. Probably no one?
That said, no idea if the duplications being addressed in this issue are related: just a
situation to keep in mind when working on this.
Hibernate pom dependency duplicates
-----------------------------------
Key: ISPN-7448
URL:
https://issues.jboss.org/browse/ISPN-7448
Project: Infinispan
Issue Type: Component Upgrade
Components: Embedded Querying, Lucene Directory
Reporter: Galder ZamarreƱo
There are multiple Hibernate dependencies duplicated in {{parent/pom.xml}} and
{{bom/pom.xml}}. Such duplication should be avoided and dependency definition should be
centralized in {{bom/pom.xml}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)