https://github.com/hibernate/hibernate-search/pull/516

You could take this to the extreme and argue that the remote backends could also go into their own modules. Not sure how useful that would be.

If it minimizes mandatory dependencies, I'd like that. But since it's a tradeoff, we don't need to make a rule of it nor need to do it in the scope of 4.4.

Note however that I would prefer to now change the jars in which the distribution is organized in 4.4. Our hope was to keep 4.4 extremely light and start working on 5.0 asap, so if this gets complex to do while keeping it in the same jar I'd postpone it to 5.0

@Guillaume Smet yes. Technically if you don't need Avro even today I think you could exclude Jackson (and Avro).

Having such things in separate modules - at least at compile & build time - should make it easier for us to make sure that such dependencies are optional.

Sanne,

Does it mean that this change would allow to remove the avro dependency from the "regular" (ie without master/slave) Hibernate Search?

Avro still uses Jackson 1.x and I wouldn't be against having lighter war files instead of having both Jackson 1.x and 2.x.