Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add java wrapper layer build #1307

Merged
merged 1 commit into from
May 3, 2024

Conversation

tylerbenson
Copy link
Member

This approach contains a few arbitrary decisions.

  • I chose to tie it to the same release job as java as they will likely always have changes together (sdk version).
  • No independent tagging for the wrapper release.
  • The underlying reported version for the wrapper layer will report --. (Since the wrapper won't have a separate release page, I think this is ok.)

This approach contains a few arbitrary decisions.
- I chose to tie it to the same release job as java as they will likely always have changes together (sdk version).
- No independent tagging for the wrapper release.
- The underlying reported version for the wrapper layer will report `--`. (Since the wrapper won't have a separate release page, I think this is ok.)
@tylerbenson tylerbenson requested a review from a team May 2, 2024 20:19
@rapphil
Copy link
Contributor

rapphil commented May 3, 2024

I chose to tie it to the same release job as java as they will likely always have changes together (sdk version).

I'm not sure if this will always be true. The java agent also includes instrumentation for a bunch of libraries no while the wrapper will only contain aws-lambda instrumentation + Otel SDK.

Having said that I think it is fine to release them together for now.

@tylerbenson tylerbenson merged commit 4a1165b into open-telemetry:main May 3, 2024
9 checks passed
@tylerbenson tylerbenson deleted the tyler/wrapper branch May 3, 2024 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants