Since 4.5.x, the handlebars artifact declares a hard OSGi import range on
jakarta.servlet [6.1,7). This breaks bundle resolution for consumers that
ship jakarta.servlet 6.0 and do not use ServletContextTemplateLoader
(the only class that depends on the servlet API).
Making the jakarta.servlet import resolution:=optional in the OSGi
manifest would allow the bundle to resolve in environments with a different
servlet API version, while retaining full functionality for users who do use
ServletContextTemplateLoader.
As a workaround we currently repackage the jar in a thin OSGi wrapper bundle
that overrides the import to resolution:=optional. We would love to be able
to drop that wrapper once this is addressed upstream.
Since 4.5.x, the
handlebarsartifact declares a hard OSGi import range onjakarta.servlet [6.1,7). This breaks bundle resolution for consumers thatship
jakarta.servlet 6.0and do not useServletContextTemplateLoader(the only class that depends on the servlet API).
Making the
jakarta.servletimportresolution:=optionalin the OSGimanifest would allow the bundle to resolve in environments with a different
servlet API version, while retaining full functionality for users who do use
ServletContextTemplateLoader.As a workaround we currently repackage the jar in a thin OSGi wrapper bundle
that overrides the import to
resolution:=optional. We would love to be ableto drop that wrapper once this is addressed upstream.