[typespec-metadata] Apply correct Java namespace prefix based on service type and flavor

[Copilot]

The typespec-metadata emitter's Java parser was returning namespaces as-is, ignoring both the TypeSpec service type (data vs. management) and the flavor emitter option. This caused incorrect Java package namespaces in the output metadata.

Prefix rules

Service type	flavor	Java namespace prefix
data	(none)	com.azure.
management	(none)	com.azure.resourcemanager.
data	azurev2	com.azure.v2.
management	azurev2	com.azure.resourcemanager.v2.

Changes

• collector.ts

  • Added applyJavaNamespacePrefix — strips any existing known Azure prefix and applies the correct one based on service type and flavor
  • Updated parseJava to accept typespecType and read flavor from emitter options
  • Updated LanguageParser type, createLanguageMetadata, buildLanguageMetadata, and collectLanguagePackages to thread typespecType through the call chain

• emitter.ts

  • Passes typespecMetadata.type to collectLanguagePackages

Example

# tsp-config.yaml for a next-gen ARM library
options:
  "@azure-tools/typespec-java":
    namespace: "com.azure.resourcemanager.contoso"
    flavor: azurev2

Previously the metadata would emit com.azure.resourcemanager.contoso. With this change it correctly emits com.azure.resourcemanager.v2.contoso.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[TypeSpec-Metadata] Java package name needs to account for "flavor"</issue_title>
<issue_description></issue_description>

<agent_instructions>Update the typspec-metadata emitter to properly add the relevant prefix to java namespaces.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes [TypeSpec-Metadata] Java package name needs to account for "flavor" #4086

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.