OSGi Core spec R5 defines in chapter 8.6 a number of attributes in osgi.identiy namespace that bindex does not support:
copyright
description
documentation
license
RFC112 defines in chapter 5.2.1 a number of Resource properties that overlap with those above to a large extent:
copyright
description
documentation
license
name
source
size
Additionally it defines in chapter 5.5.6 tag
Looking at index files generated by maven-bundle-plugin, using old bindex, I can see that it puts presentationname attribute into tag, and presentationname and manifestversion attributes into 'bundle' capability. Those are not mentioned explicitly in RFC112 but have well known meaning
Some of the above properties have corresponding Manifest headers:
copyright: Bundle-Copyright
description: Bundle-Description
license: Bundle-License
name/presentationname: Bundle-Name
category: Bundle-Category
manifestversion: Manifest-Version
size is already supported by bindex 2 in osgi.content namespace, and source property is inherently incompatible. RFC112 mandates a mechanism based on URLs and OSGi Core R5 a mechanism based on requirements (see chapter 8.6.1)
I'm planning to use the headers mentioned in the last list above to define additional attributes in osgi.identiy namespace and include them into the indexes
OSGi Core spec R5 defines in chapter 8.6 a number of attributes in osgi.identiy namespace that bindex does not support:
RFC112 defines in chapter 5.2.1 a number of Resource properties that overlap with those above to a large extent:
Looking at index files generated by maven-bundle-plugin, using old bindex, I can see that it puts presentationname attribute into tag, and presentationname and manifestversion attributes into 'bundle' capability. Those are not mentioned explicitly in RFC112 but have well known meaning
Some of the above properties have corresponding Manifest headers:
size is already supported by bindex 2 in osgi.content namespace, and source property is inherently incompatible. RFC112 mandates a mechanism based on URLs and OSGi Core R5 a mechanism based on requirements (see chapter 8.6.1)
I'm planning to use the headers mentioned in the last list above to define additional attributes in osgi.identiy namespace and include them into the indexes