ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-365) OBR non-bundle metadata has no symbolicname/version metadata
Date Tue, 25 Jun 2013 13:10:21 GMT


Marcel Offermans commented on ACE-365:

As a heuristic, I can live with that. However, I don't agree that in general every type of
artifact has a version. For bundles, this is clear: their metadata contains both a BSN and
version. For other artifacts, it is not so clear (for example, a JPEG file). So I agree we
can give them an identity, we can even give them a version (if we like) but we should not
rely on everything in the world to be versioned (semantically). I believe that should be a
separate discussion though, so +1 on this issue.
> OBR non-bundle metadata has no symbolicname/version metadata
> ------------------------------------------------------------
>                 Key: ACE-365
>                 URL:
>             Project: ACE
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Bram de Kruijff
> Although the ACE OBR support uploading non-bundle resources based on the filename :=
<bsn>-<version>.<ext>  heuristic, this metadata is not reflected in the
respository.xml index. Infact it only species the resource.uri.
> As a result it is impossible to find these resources by querying the repository in a
sensible way, such as using a requirement with an osgi.identity=<bsn> filter directive.
> Therefore, I suggest to at least add the resource.symbolicname and resource.version to
the current implementation. This is in line with R5 where every resource will have an osgi.identity
and osgi.content namespace capability.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message