You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/01/31 10:00:13 UTC
[jira] Created: (KARAF-426) Manage Karaf shell.name by branding
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é
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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (KARAF-426) Manage Karaf shell.name by branding
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-426.
----------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
2.2.0
Revision 1065564.
> 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é
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (KARAF-426) Manage Karaf shell.name by branding
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-426:
------------------------------------------
Assignee: Jean-Baptiste Onofré
> 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é
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-426) Manage Karaf shell.name by branding
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988712#comment-12988712 ]
Jean-Baptiste Onofré commented on KARAF-426:
--------------------------------------------
Karaf Console alrady manage ${USER} and ${APPLICATION} variable in the PROMPT.
> 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é
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (KARAF-426) Manage Karaf shell.name by branding
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-426.
--------------------------------
> 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é
> 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 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
[jira] Work started: (KARAF-426) Manage Karaf shell.name by
branding
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KARAF-426 started by Jean-Baptiste Onofré.
> 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é
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-426) Manage Karaf shell.name by branding
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988700#comment-12988700 ]
Jean-Baptiste Onofré commented on KARAF-426:
--------------------------------------------
The branding.properties file could contain a prompt property.
The prompt property should support ASCII and "special" string for instance:
\u001B[1mmy_user\u001B[0m@${karaf.name}>
> 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é
>
> 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira