[
https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860004#comment-16860004
]
ASF subversion and git services commented on KARAF-426:
-------------------------------------------------------
Commit 0922fef53639a6cc96199fb89cbb210eb0897bdf in karaf-site's branch
refs/heads/trunk from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf-site.git;h=0922fef ]
Merge pull request #43 from fpapon/RELEASE-KARAF-426
Release Karaf Runtime 4.2.6
> Manage Karaf shell.name by branding
> -----------------------------------
>
> Key: KARAF-426
> URL: https://issues.apache.org/jira/browse/KARAF-426
> Project: Karaf
> Issue Type: New Feature
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 2.2.0, 3.0.0
>
>
> Currently, when you start Karaf (or connect remotely to a karaf instance),
> you get a shell looking like:
> karaf@root>
> The "root" is the karaf instance name and could be changed using the
> karaf.name property defined in etc/system.properties file.
> The "karaf" part is hard coded in Karaf and not yet linked to users defined
> (especially when you enable some JAAS support using a database or LDAP
> backend :)).
> We can consider this "karaf" as a shell name, and we could consider this as
> linked to the branding.
> Karaf branding is looking for a org/apache/karaf/branding/branding.properties
> file containing a welcome property.
> This property is used by the Karaf branding support (at bootstrap) to display
> the welcome message.
> I propose to extend this branding.properties file by adding another
> shell.name property defining the shell name.
> If the property is not found or null, we fall back to "karaf" as it is
> currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
