0.3.0-RC1

Breaking changes

• Deprecated dd-trace.yaml config has been removed. Going forward, config must be done using environment variables or system properties (#183)
• Artifact names have changed: (#184)
  • dd-trace -> dd-trace-ot
  • dd-trace-annotations -> dd-trace-api
• Package names have been standardized: (#184)
  • datadog.trace
  • datadog.opentracing
• OpenTracing bindings have been upgraded to 0.31.0. If you need support for 0.30.0, consider using the compatibility layer (#126)

Bugfixes

• Prevent ClassNotFoundException by ensuring consistent load order of helper classes. (#187 #190 #194)

Migrate from 0.2.x to 0.3.0-RC1

• If you're only using dd-java-agent then you only need to migrate your configuration. Reference your dd-trace.yaml file and set the appropriate environment variables or system properties according to your application server. System properties can usually be set along side the javaagent flag.
• If you're using the @Trace annotation, you will need to:
  • Update the artifact name in your gradle or maven config
  • Replace package names from import com.datadoghq.trace.Trace to import datadog.trace.api.Trace
• If you're using the OpenTracing bindings, you'll need to update how the DDTracer is created. Instead of using DDTracerFactory, you should call a DDTracer constructor directly. Alternatively, you could consider using TracerResolver.

For example:

Tracer tracer = DDTracerFactory.createFromConfigurationFile();
io.opentracing.util.GlobalTracer.register(tracer);

Would change to:

Tracer tracer = new DDTracer();
io.opentracing.util.GlobalTracer.register(tracer);

For assistance migrating manual instrumentation, please contact support.