shouldn't have a hard-dependency on a <1.0 api

[codefromthecrypt]

Even when not using tracing, opencensus 0.18 types are required per this line in HttpRequest

  /** OpenCensus tracing component. */
private final Tracer tracer = OpenCensusUtils.getTracer();

grpc code is more defensive to not require loading classes until used.

[elharo]

Relevant: https://github.com/GoogleCloudPlatform/cloud-opensource-java/blob/master/library-best-practices/JLBP-4.md

[codefromthecrypt]

why is this a question and not a bug?

[bogdandrutu]

OpenCensus versions <1.0 should be treated as any version >1.0. In the OpenCensus project we made a decision to respect all the requirements for versions >1.0 which means we do not break compatibility (remove classes/methods or change signatures).

So this should be closed.

[elharo]

If that's so, you might as well go ahead and release 1.0. However I have to note that for an allegedly stable product, the different versions of OpenCensus have caused us a lot of trouble.

[codefromthecrypt]

Even if there is no argument about version drift etc, it is still completely unnecessary for this code to be called in absence of any setup instructions. 1.0 or not, it is pulling unnecessary dependencies into the application, and for no reason as the tracer isn't used.

[codefromthecrypt]

the typical way to fix accidental classpath leak is to make a separate class that has the stuff inside. There are varying approaches to this. For example armeria recently made it possible to not have dropwizard in the classpath via this change line/armeria#2107

At some point, there might be some RPC library that you also find troublesomely hard pinned to something you don't want or use. I hope pointers on technical solution is helpful.