You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OSGi manifest headers missing from published JARs since 26.0 #4547
Since 26.0, the published graphql-java JAR no longer contains OSGi headers (Bundle-SymbolicName, Bundle-Version, Export-Package, Import-Package). As a result, it can't be deployed as a bundle in an OSGi container, and downstream bundles built with bnd no longer get version ranges on their graphql.* imports.
This appears to have been introduced by 4db3cc4 (#4171, Gradle 9.2.0 upgrade). That's the only change to the bnd setup between 25.0 and 26.0. The previous setup was:
The bnd builder plugin only adds BundleTaskExtension to the jar task, so on shadowJarfindByType returns null and the block is skipped silently. The doLast { buildBundle() } step was also dropped, so bnd never rewrites the manifest.
Suggested fix
The bnd Gradle plugin documents this pattern for tasks other than jar:
I haven't built graphql-java with this change, so it's a suggestion, not a tested patch. A build check that fails if Bundle-SymbolicName is missing from the shadow JAR would stop this from happening again.
Activity