You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project has been deprecated.
A version 0.1.1 was built that can be used in projects that still have a dependency to avoid having multiple physical global tracer instances.
Tracer resolution has been moved to the TracerResolver contrib project.
The artifacts should probably remain on maven-central.
Should we rename this contrib repository? Simply delete it from github? Clearly, I don't know what is the best course of action.
@bhs or others, do you have any experience on this sort of thing?
The text was updated successfully, but these errors were encountered:
@sjoerdtalsma IMO the README should have a deprecation warning front-and-center (with appropriate redirects to the main OT-Java and TracerResolver repos where these ideas ultimately landed) and someone should create a calendar event to delete the repo outright in ~6 months or so.
Def a judgement call, though, and I can see lots of other possible courses of actions. I def wouldn't bother meddling with artifacts in maven-central... not much upside to doing that.
The project has been deprecated.
A version
0.1.1
was built that can be used in projects that still have a dependency to avoid having multiple physical global tracer instances.Tracer resolution has been moved to the TracerResolver contrib project.
The artifacts should probably remain on maven-central.
Should we rename this contrib repository? Simply delete it from github?
Clearly, I don't know what is the best course of action.
@bhs or others, do you have any experience on this sort of thing?
The text was updated successfully, but these errors were encountered: