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

To migrate project to gradle and use Muzzle OTEL Gradle plugin #625

Open
lgajowy opened this issue Mar 1, 2023 · 1 comment
Open

To migrate project to gradle and use Muzzle OTEL Gradle plugin #625

lgajowy opened this issue Mar 1, 2023 · 1 comment
Assignees
Labels
Milestone

Comments

@lgajowy
Copy link
Contributor

lgajowy commented Mar 1, 2023

Why?

The OpenTelemetry project uses gradle. It also provides a Gradle plugin - Muzzle, that detects resources (classes) that are necessary to be on the classpath when the javaagent is run (avoiding constant NoClassDefFound/ClassNofFound exceptions). It also helps finding and using Virtual fields which we use extensively. If we use gradle, we could just use it and have codebase reduced - currently we manually list classes that should be included which is cumbersome.

Other reasons:
Potentially new gradle plugins could be developed by OTEL project and we could use them too
Gradle is easier to use (and faster?)

Alternatives:
Write our own sbt Muzzle plugin. This would require us to maintain it though which is a downside imho and a big distractor.

@lgajowy lgajowy added this to the 0.9.0 milestone Mar 1, 2023
@lgajowy lgajowy self-assigned this Mar 15, 2023
@ptrdom
Copy link
Member

ptrdom commented Mar 16, 2023

Relevant findings - #353 (comment).

@adamgadomski adamgadomski changed the title R&D: Migrate project to gradle and use Muzzle OTEL Gradle plugin To migrate project to gradle and use Muzzle OTEL Gradle plugin Mar 16, 2023
@adamgadomski adamgadomski modified the milestones: 0.9.0, 0.10.0 Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants