1
87%
master: 87%

Ran 19 Mar 2018 03:23PM UTC

Files 360

Run time 27s

Badge

Embed ▾

Committed 19 Mar 2018 01:43PM UTC coverage: 79.64% (+0.2%) from 79.42%

Job # 298.1

Build Type

push

travis-ci

Committed by

yrodiere

Commit Message

Make annotation discovery a global setting

The previous implementation tried to be smart, discovering nested type
annotations when processing annotation mapping, and ignoring them when
processing programmatic mapping.

But the approach was fundamentally flawed: some of the discovered
metadata is cached, and shared between all the mappings. For instance
this is the case of markers. So with the previous approach, discovered
annotations could impact a programmatic mapping or not depending on
whether they were discovered before or after the programmatic mapping
was processed. Which can be terribly confusing.

Thus I gave up and made annotation discovery a global setting: either
you enable it everywhere (in annotation and programmatic mappings),
or you don't enable it at all.

The original goal of this switch was to allow people with annotated
classes to ignore the annotations and only rely on a programmatic
mapping, so I also added a setting in the ORM integration to disable
annotation mapping completely.

Coverage Stats

4862 of 6105 relevant lines covered (79.64%)

0.8 hits per line

hibernate / hibernate-search-6-poc / 298 / 1
87%
master: 87%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 298.1

hibernate / hibernate-search-6-poc / 298 / 1 87% master: 87%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 298.1

hibernate / hibernate-search-6-poc / 298 / 1
87%
master: 87%

README BADGES
x