aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARIES-965) Consider having the subsystems api bundle include the org.osgi.service.repository package and both import and export it.
Date Mon, 26 Nov 2012 16:44:57 GMT

     [ https://issues.apache.org/jira/browse/ARIES-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Ross resolved ARIES-965.
-----------------------------

    Resolution: Fixed

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1413711.
                
> Consider having the subsystems api bundle include the org.osgi.service.repository package
and both import  and export it.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-965
>                 URL: https://issues.apache.org/jira/browse/ARIES-965
>             Project: Aries
>          Issue Type: Improvement
>          Components: Subsystem
>            Reporter: John Ross
>            Assignee: John Ross
>
> Without installing an implementation of the OSGi Repository specification, there is currently
no other way of getting the org.osgi.service.repository package than the osgi.enterprise jar.
Subsystems does not require an implementation of the repository specification in order to
function, but it does require the package since it uses repositories internally (e.g., local,
system, and preferred provider). It therefore seems reasonable to include that package in
the subsystems api bundle. This would also be helpful to subsystems users who will make use
of the repository api but don't need a standard spec implementation.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message