[jboss-jira] [JBoss JIRA] (WFLY-3828) Backport CLI preference, .jbossclirc

[Osamu Nagano (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000125#comment-13000125 ] 

Osamu Nagano commented on WFLY-3828:
------------------------------------

This is accidentally created, it should be filed against PRODMGT.  Closing.

> Backport CLI preference, .jbossclirc
> ------------------------------------
>
>                 Key: WFLY-3828
>                 URL: https://issues.jboss.org/browse/WFLY-3828
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: CLI
>            Reporter: Osamu Nagano
>            Assignee: Alexey Loubyansky
>
> 1. Proposed title of this feature request  
> Backport CLI preference, .jbossclirc
>   
> 2. Who is the customer behind the request?  
> Account: USSTRATCOM (1018342)
> TAM customer: no
> SRM customer: no
> Strategic: no
>   
> 3. What is the nature and description of the request?  
> Current CLI can define an alias.  For example, {{alias ll="ls -l"}}.  But such alias doesn't persist among different CLI sessions.  In WildFly, CLI reads ".jbossclirc" during its startup and it can be served to save preferences like aliases.
>   
> 4. Why does the customer need this? (List the business requirements here)  
> - To avoid typing the same alias every time.
>   
> 5. How would the customer like to achieve this? (List the functional requirements here)  
> - By defining preferences in ".jbossclirc" file.
>   
> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
> - Start a new CLI session to see whether a defined alias is available or not.
>   
> 7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
> https://issues.jboss.org/browse/WFLY-1063
> https://bugzilla.redhat.com/show_bug.cgi?id=1139111
>   
> 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
> If possible, in EAP 6.4.
>   
> 9. Is the sales team involved in this request and do they have any additional input?  
> No.
>   
> 10. List any affected packages or components.  
> - EAP
>   
> 11. Would the customer be able to assist in testing this functionality if implemented?  
> No (a customer test is not required).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)