SpringSource manifest headers registered with OSGi

The OSGi Alliance has decided to accommodate vendor-specific manifest headers by listing them in a public registry. The aim is to avoid clashes between vendors and between vendors and OSGi’s own headers.

The registry currently contains OSGi’s own headers, those introduced by SpringSource dm Server, and two used by the bnd tool.

comments powered by Disqus