[
https://issues.apache.org/jira/browse/FELIX-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-568.
-------------------------------------
Resolution: Won't Fix
Thanks for supplying these patches.
But as the bundles page has been refactored to support RESTful URLs (see
FELIX-566) I think is issue does not need to be applied.
Please close this issue, if you agree. Thanks.
> [Patch] Separate bundle details page in sling web console
> ---------------------------------------------------------
>
> Key: FELIX-568
> URL: https://issues.apache.org/jira/browse/FELIX-568
> Project: Felix
> Issue Type: New Feature
> Components: Web Console
> Reporter: Alexander Klimetschek
> Assignee: Felix Meschberger
> Attachments: bundle-details-html-page.patch,
> bundle-details-html-page.patch, bundle-details-html-page.patch,
> show-bundle-details.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> This patch adds a separate HTML page showing bundle details to the Sling web
> console. It displays the same details as those displayed by the ajax-based
> "popup".
> Use case: I found myself configuring a bundle with Export-Package etc. and
> continuously installing it to Sling to see if all package dependencies could
> be resolved. It is quite tedious to reload the bundle list page, scroll down
> to the bundle in question and click on the link to get the ajax-based details
> popup. A simpler (and more restful) way is to have a separate URL and HTML
> page for a single bundle's details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
