On Fri, 19 Aug 2011 18:50:34 +0200, Emmanuel Bernard <emman...@hibernate.org> wrote:
> There are unforeseen consequences to making Avro an optional dependency. > By doing that, I must make the SerializerProvider build process lazy or > tolerant at Runtime if Avro is not here. > The problem with this approach is that if a user forgets to add Avro as > a dependency, his system will fail the first time a message ought to be > (de)serialized *at runtime* Is this > It forces us to introduce an explicit flag to be set y the user to know > whether or not the SerializationProvider is required > > hibernate.search.indexname.serializer required > > I find that quite error prone and am inclined to think that leaving Avro > a required dependency is the less of two evils. Right. That no good option at all. Then I rather have Avro required. However, this also means that if someone uses an alternative/homegrown SerializerProvider, he still ends up w/ Avro as well (at least from a maven point of view) _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
