Uploaded image for project: 'Hibernate Search'
  1. HSEARCH-2597

Do not rely on automatic detection of JPA annotations from the classpath

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.7.0.Final
    • Component/s: engine, integration
    • Labels:
      None

      Description

      The Hibernate Search engine, which is supposedly independent from Hibernate ORM, is actually changing its mapping semantics (and validations) depending on the presence (or not) of some key JPA annotations for historical reasons.

      This represents an inconsistent behaviour for some integrators not relying on Hibernate ORM, as the presence (or not) of some other third party dependency will influence the mapping validation.

      Now that the JPA API is no longer an optional dependency of Hibernate ORM, we should switch this to an explicit (internal) configuration setting controlled by the SearchIntegrator.

      By cleaning this up I also happened to find some inconsistencies in our tests.

        Attachments

          Activity

            People

            • Assignee:
              sanne Sanne Grinovero
              Reporter:
              sanne Sanne Grinovero
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: