From d53ac394fb9ec340cea7594f263a1d14cf44be15 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn=20Darri=20Sigur=C3=B0sson?= Date: Wed, 8 Oct 2025 18:15:11 +0000 Subject: [PATCH] fix: use valid JPMS module name for mcp-core MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changed Automatic-Module-Name from io.modelcontextprotocol.sdk.mcp-core to io.modelcontextprotocol.sdk.mcp.core. JPMS module names must be valid Java identifiers and cannot contain dashes. This was preventing usage in modular Java applications. The OSGI Bundle-SymbolicName is kept as io.modelcontextprotocol.sdk.mcp-core (with dash) for backward compatibility, as OSGI allows dashes in symbolic names. Note: If preferred, the Automatic-Module-Name could use BND's substitution macro instead: ${subst;${project.groupId}.${project.artifactId};-;.} 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- mcp-core/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mcp-core/pom.xml b/mcp-core/pom.xml index 5681385b6..1e188195c 100644 --- a/mcp-core/pom.xml +++ b/mcp-core/pom.xml @@ -38,7 +38,7 @@ version: ${versionmask;===;${version_cleanup;${project.version}}} Bundle-SymbolicName: ${project.groupId}.${project.artifactId} Bundle-Version: ${version} - Automatic-Module-Name: ${project.groupId}.${project.artifactId} + Automatic-Module-Name: io.modelcontextprotocol.sdk.mcp.core Import-Package: jakarta.*;resolution:=optional, \ *; Export-Package: io.modelcontextprotocol.*;version="${version}";-noimport:=true