opentelemetry-go/example/jaeger/go.mod

module go.opentelemetry.io/otel/example/jaeger

go 1.13

replace (
	go.opentelemetry.io/otel => ../..
	go.opentelemetry.io/otel/exporters/trace/jaeger => ../../exporters/trace/jaeger
)

require (
	go.opentelemetry.io/otel v0.4.2
	go.opentelemetry.io/otel/exporters/trace/jaeger v0.4.2
)
Namespace import path under "/otel" (#274) Also fixes example module paths so that they use the vanity URL instead of the github URL. [Closes #184] 2019-11-01 11:40:29 -07:00			`module go.opentelemetry.io/otel/example/jaeger`
Automate getting the list of examples to build (and switch to go 1.13 to avoid module problems) (#246) * automate building all the examples the EXAMPLES variable was out of date - the stackdriver example wasn't even built let's automate it, so we don't need to remember about updating the variable after adding a new example to the examples directory * move jaeger example to example directory this should be in the examples directory, so it can be built by the make test during CI. * switch to go 1.13 circle ci uses go 1.12 (which is the oldest 1.12 release) that contains some bugs with module handling let's switch to go 1.13.3, the latest go currently * use a single valid revision of the project in go.mod files this probably shouldn't be a problem since the switch to go 1.13 in circle ci, but cleans up the mess and the use of bogus releases 2019-10-29 16:45:48 +01:00
			`go 1.13`

			`replace (`
Namespace import path under "/otel" (#274) Also fixes example module paths so that they use the vanity URL instead of the github URL. [Closes #184] 2019-11-01 11:40:29 -07:00			`go.opentelemetry.io/otel => ../..`
Rename the exporter directory to exporters (#502) The `go.opentelemetry.io/otel/exporter/trace/jaeger` package was mistakenly released with a `v1.0.0` tag instead of `v0.1.0`. This resulted in all subsequent releases not becoming the default latest, meaning that `go get`s pulled in the incompatible `v0.1.0` release of that package when pulling in more recent packages from other otel packages. Renaming the `exporter` directory to `exporters` fixes this issue by consequentially renaming the package. Additionally, this action also renames all exporters. This is understood to be a disruptive action to existing users as they will need to update any dependencies they currently have on our exporters. However, it was decided to take this action regardless. The need to resolve the existing issue explained above is highly important, and given the Alpha state of this project these kinds of breaking changes should be expected (though not without reason). Resolves #331 Co-authored-by: Rahul Patel <rghetia@yahoo.com> 2020-03-02 13:54:57 -08:00			`go.opentelemetry.io/otel/exporters/trace/jaeger => ../../exporters/trace/jaeger`
Automate getting the list of examples to build (and switch to go 1.13 to avoid module problems) (#246) * automate building all the examples the EXAMPLES variable was out of date - the stackdriver example wasn't even built let's automate it, so we don't need to remember about updating the variable after adding a new example to the examples directory * move jaeger example to example directory this should be in the examples directory, so it can be built by the make test during CI. * switch to go 1.13 circle ci uses go 1.12 (which is the oldest 1.12 release) that contains some bugs with module handling let's switch to go 1.13.3, the latest go currently * use a single valid revision of the project in go.mod files this probably shouldn't be a problem since the switch to go 1.13 in circle ci, but cleans up the mess and the use of bogus releases 2019-10-29 16:45:48 +01:00			`)`

			`require (`
Prepare for releasing v0.4.2 (#608) 2020-03-31 12:57:37 -07:00			`go.opentelemetry.io/otel v0.4.2`
			`go.opentelemetry.io/otel/exporters/trace/jaeger v0.4.2`
Automate getting the list of examples to build (and switch to go 1.13 to avoid module problems) (#246) * automate building all the examples the EXAMPLES variable was out of date - the stackdriver example wasn't even built let's automate it, so we don't need to remember about updating the variable after adding a new example to the examples directory * move jaeger example to example directory this should be in the examples directory, so it can be built by the make test during CI. * switch to go 1.13 circle ci uses go 1.12 (which is the oldest 1.12 release) that contains some bugs with module handling let's switch to go 1.13.3, the latest go currently * use a single valid revision of the project in go.mod files this probably shouldn't be a problem since the switch to go 1.13 in circle ci, but cleans up the mess and the use of bogus releases 2019-10-29 16:45:48 +01:00			`)`