* Generate bootstrap jar with gradle instead of when running tests.
* kill all semicolons
* docs
* docs
* ByteCodeTest
* Use latestDepTest classpath for its bootstrap jar
* Rename package
* Reformat comment
* Bootstrap jar absolute path
* Save bootstrap jar to reports dir.
* Debug
* Debug
* Use project.getBuildDir
* Restore
* Revert
* testFieldInjection is instrumentation test too.
* Split out bytecode tests for testing-common
* Apply jacoco configuration to all tests.
* Add note that jacoco may be causing frustration.
* YOLO alert - Hope my guess at the reason is correct
* Apply suggestions from code review
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
Co-authored-by: Trask Stalnaker <trask.stalnaker@gmail.com>
* Now publish all instrumentations as well.
Changed groupId to `io.opentelemetry.instrumentation`.
Removed `opentelemetry` from auto-exporters' artifactIds.
Some instrumentations will need moving around to have better names, e.g. servlets. Should I do it right away?
* Polish
* Unify names of published artifacts
* Renamed some modules
* Fix CI config
* Rename project-reactor back to reactor
* Allow compiling of everything with java 11
* Instruct CircleCI to use java 11 be default
* Forbid running some tests on java11
* Muzzle uses ClassLoader.platformClassLoader as parent for user-space classloader
* Rename hibernate modules
* Update tracer name
* Change from gradle inheritance to composition
This will make it possible to have empty "grouping" modules, e.g.
instrumentation:hibernate.
* Introduce empty hibernate grouping module
Trask Stalnaker
Anuraag Agrawal
Nikita Salnikov-Tarnovski
Tyler Benson