You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/07/19 13:38:34 UTC
[jira] [Resolved] (SLING-2528) Allow resources to be queried from
the OSGi Installer service
[ https://issues.apache.org/jira/browse/SLING-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2528.
-------------------------------------
Resolution: Fixed
Fix Version/s: Installer Core 3.3.8
I've added a new service interface, together with some interfaces to get the current state.
The new service provides all available information
The web console plugin now uses this interface as well instead of doing internal calls
> Allow resources to be queried from the OSGi Installer service
> -------------------------------------------------------------
>
> Key: SLING-2528
> URL: https://issues.apache.org/jira/browse/SLING-2528
> Project: Sling
> Issue Type: New Feature
> Components: Installer
> Affects Versions: Installer Core 3.3.6
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.3.8
>
>
> The OsgiInstaller service currently only allows for resource registration and update. It would be interesting to have a query interface to ask the OsgiInstaller service for currently installed resources:
> // known resources or empty array if none
> InstallableResource[] getResources();
> This could for example be used to expose the bundles known to the OSGi Installer as a Maven Repository for simple setup of a development environment based on an existing Sling instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira