Is the Elastic APM Java Agent about to be replaced by the OTel agent?

[linghengqian]

• I noticed that issues like [META 882] Check classic and OTel agents against serverless · Issue #3744 · elastic/apm-agent-java · GitHub refer to the Elastic APM Java Agent as a classic agent.
• Does the wording of classic mean that the Elastic APM Java Agent will be deprecated soon? After all, the Elastic-style OTel Java agent can accomplish the same thing.
• 

[Jack_Shirazi]

If you are starting a new project, and the features in the Elastic Distribution of OpenTelemetry Java agent (EDOT Java agent) provide what you need for your observability requirements, we recommend using that agent in preference to the Elastic APM Java Agent (classic Java agent).

Both agents are currently maintained. We have no immediate plans to deprecate the classic Java agent, it is used extensively by many customers. Once we've ported the majority of the features available from the classic Java agent into the EDOT Java agent (and the upstream OpenTelemetry Java agent where possible, where we've already contributed a number of our features), then the EDOT Java agent will be more fully featured and cover more instrumentations than classic Java agent, as the EDOT Java agent will have a superset of both the OpenTelemetry Java agent and the classic Java agent