Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

duplicated opentelemetry packages

Open
#342 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start by reviewing api/src/main/proto and the referenced opentelemetry-proto-java dependency, then reproduce the reported Maven dependency:analyze and jdeps output for api-1.0.41.jar. The work is done when the control-plane artifact no longer duplicates the OpenTelemetry classes or forces unrelated modules to import control-plane packages.

Written by the indexing model from the issue text.

Description

Problem
It looks like java-control-plane replicates opentelemetry-proto-java without relocating the dependencies (i.e. you folks use the same package and class names). This duplicates the classes such that now that we've added the io.envoyproxy.controlplane dependency to a core library, maven's dependency:analyze tool is forcing us to import io.envoyproxy.controlplane in modules that do not interact with controlplane code at all. In a few places, we were forced to replace the opentelemetry import with envoyproxy.controlplane. Our (pruned) jdeps output reveals this issue:

jdeps -verbose --class-path ~/.m2/repository/io/envoyproxy/controlplane/api/1.0.41/api-1.0.41.jar  path/to/now_requires_controlplane_import.jar | grep 'api-1.0.41.jar'

now_requires_controlplane_import.jar -> /Users/joy.bestourous/.m2/repository/io/envoyproxy/controlplane/api/1.0.41/api-1.0.41.jar
<FILE IN JAR> -> io.opentelemetry.proto.common.v1.AnyValue          api-1.0.41.jar
...

Solution Requested
We're hoping you folks could either depend directly on opentelemetry-proto or use a different package to avoid this duplication and subsequent maven confusion.

Thanks in advance!

Dominant language
Java
Stars
312
Forks
150
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/java-control-plane

All issues in envoyproxy/java-control-plane

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.