We're updating the issue view to help you get more done. 

Use a consistent strategy to decide on the package hosting each annotation

Description

We have several inconsistencies:

  • Bridge-related annotations are in the org.hibernate.search.mapper.pojo.bridge.declaration package, close to all other bridge-related APIs

  • ... except IdentifierBridgeRef and ValueBridgeRef, which are in the org.hibernate.search.mapper.pojo.mapping.definition.annotation package

  • ContainerExtraction and ContainerExtract are in the org.hibernate.search.mapper.pojo.mapping.definition.annotation package, even though most other APIs related to container extractors are in the org.hibernate.search.mapper.pojo.extractor package.

  • and so on.

We should decide on a single strategy and apply it for everything:

  • either annotations are in an annotation sub-package under the package that hosts related APIs

  • or all annotations of the POJO module are in a single package.

Environment

None

Status

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Components

Fix versions

Priority

Major