On Fri, 19 Aug 2011 18:50:34 +0200, Emmanuel Bernard
There are unforeseen consequences to making Avro an optional
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* as opposed to fail at configuration time.
sorry, in my previous email I accidentally sent before being finished
I don't think that it is really a big issue that thing will only fail at
There would be a simple error message telling you that there is no
and it should not be too hard to add the right jars.