[
https://issues.apache.org/jira/browse/SLING-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718218#comment-13718218
]
Carsten Ziegeler commented on SLING-2976:
-----------------------------------------
For name vs description - yes, both are human consumable, a short and a long
version.
For the API, I see your point, however if we change this to a configuration and
Config Admin - still every consumer can change this through the Config Admin.
It's a little bit more hidden but still doable.
But I'm wondering why I didn't use a configuration and went the data file
way....must have been the heat :) - or in short, +1 for configuration
> Add support for instance name and description
> ---------------------------------------------
>
> Key: SLING-2976
> URL: https://issues.apache.org/jira/browse/SLING-2976
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions Settings 1.2.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Settings 1.2.4
>
>
> With the introduction of the topology API, we added support for two framework
> properties sling.name and sling.description. Right now, these values need
> either be set as system properties or in the sling.properties file.
> There are two issues with these:
> - we don't have any default values
> - they are not changeable at run time
--
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
