The tracing APIs vary from version to version significantly. That puts a lot of extra effort on the person updating the included packages. How important are those now we're transitioning to use an external dependency?
On Fri, Mar 4, 2016 at 5:17 PM Josh Elser <[email protected]> wrote: > Maybe the distributed tracing APIs? > > Christopher wrote: > > Sure, we can include that. Are there any other classes which would be > > good to have javadocs for which aren't public API? > > > > On Fri, Mar 4, 2016 at 4:03 PM Josh Elser <[email protected] > > <mailto:[email protected]>> wrote: > > > > Good catch, Dan. Thanks for letting us know. Moving this one over to > the > > dev list to discuss further. > > > > Christopher, looks like it might also be good to include iterator > > javadocs despite not being in public API (interfaces, and > > o.a.a.c.i.user?). > > > > -------- Original Message -------- > > Subject: 1.6 Javadoc missing classes > > Date: Fri, 4 Mar 2016 15:59:26 -0500 > > From: Dan Blum <[email protected] <mailto:[email protected]>> > > Reply-To: [email protected] <mailto:[email protected]> > > To: <[email protected] <mailto:[email protected]>> > > > > A lot of classes seem to have gone missing from > > http://accumulo.apache.org/1.6/apidocs/ - SortedKeyValueIterator > > would be an > > obvious example. > > >
