Yeah perhaps we should do that. The problem we had before was that we hadn't seperated the user-facing versus non-user-facing classes so there were like 10k scala classes. It was pretty overwhelming.
-Jay On Thu, Jan 30, 2014 at 4:55 AM, David Arthur <mum...@gmail.com> wrote: > Yea, I thought the Scaladocs for 0.7 were perfectly fine. Even with > Javadocs for the new clients won't help with lower level classes that are > exposed in those APIs (e.g., KeyedMessage) > > > On 1/30/14 6:26 AM, Kostya Golikov wrote: > >> Why not use *scala*doc then? It is way prettier than javadoc >> >> >> 2014-01-30 Jay Kreps <jay.kr...@gmail.com>: >> >> The primary problem was that we never found a way to get sane javadocs >>> for >>> scala code. Moving the clients out of scala will fix this (e.g. >>> >>> http://empathybox.com/kafka-javadoc/index.html?kafka/clients/producer/ >>> KafkaProducer.html >>> ) >>> >>> -Jay >>> >>> >>> On Wed, Jan 29, 2014 at 11:54 AM, David Arthur <mum...@gmail.com> wrote: >>> >>> Noticed these are no where to be found on the webpage. Are we currently >>>> publishing these anywhere? >>>> >>>> -David >>>> >>>> >
