Fix empty Bundle-SymbolicName in OSGi manifest (regression from 3.0.0)

[Copilot]

The OSGi manifest in 3.0.1 has an empty Bundle-SymbolicName and incorrect Bundle-Version: 0, breaking OSGi compatibility. This is a regression from 3.0.0 where these fields were correctly populated.

Root Cause

The spec-version-maven-plugin was removed from the <plugins> section during the 3.0.0→3.0.1 upgrade (remained only in <pluginManagement>). This prevented the plugin from executing and generating the properties that maven-bundle-plugin uses to populate the manifest.

Changes

Re-activated spec-version-maven-plugin in api/pom.xml:

<plugins>
    <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>buildnumber-maven-plugin</artifactId>
    </plugin>
    <plugin>
        <groupId>org.glassfish.build</groupId>
        <artifactId>spec-version-maven-plugin</artifactId>
    </plugin>
    <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
    </plugin>

This restores the manifest fields to their 3.0.0 values:

• Bundle-SymbolicName: jakarta.json.bind-api
• Bundle-Version: 3.0.1
• Extension-Name: jakarta.json.bind
• Implementation-Version: 3.0.1
• Specification-Version: 3.0

Fixes jakartaee#357

Original prompt

Analyze and fix jakartaee#357

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.