Closed ErikKoppenhagen closed 4 years ago
As this is not standardized in OSGi and therefore not used in many example OSGi projects, this seems to be a very specific use case that requires the projects to follow this hierarchical bundle category naming scheme just to use a feature like this. Default suggestions for bundle category names are listed by the OSGi alliance here and don't suggest this to be a feature. Closed and won't do.
A boundle may have multiple boundle categories. These categories might have different contexts, e.g. one category defines its architectural layer, the other one its business context. These contexts (or types) of boundle categories could be defined by using a colon:
Because it wouldn't make sense to have them all shown in the same bundle category view, each type requires their on view. For the given data this could be as following:
This is linked to issues 7, 8 and 11