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 2010/02/04 11:38:28 UTC
[jira] Updated: (SLING-983) Add sling.properties file to
configuration status page
[ https://issues.apache.org/jira/browse/SLING-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-983:
-----------------------------------
Component/s: (was: General)
Engine
Affects Version/s: Launchpad Base 2.1.0
Fix Version/s: Engine 2.1.0
Launchpad Base 2.2.0
We add two new properties "sling.properties" and "sling.properties.url" pointing to the properties file, the first one contains the file path and the second a url
(like sling.home and sling.home.url)
The sling engine will get a new configuration printer which takes this property, reads the resource from the url and displays its content.
> Add sling.properties file to configuration status page
> ------------------------------------------------------
>
> Key: SLING-983
> URL: https://issues.apache.org/jira/browse/SLING-983
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Launchpad Base 2.1.0
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Fix For: Launchpad Base 2.2.0, Engine 2.1.0
>
>
> It would be good, if the sling.properties file could be provided through a Felix Web Console ConfigurationPrinter to include it into the Configuration Status output to ease support.
> Maybe this would be part of the Sling Engine bundle, which is the "core engine" of Sling.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.