[overlord-issues] [JBoss JIRA] (SRAMP-474) CLI: Add a log-to-file option

Brett Meyer (JIRA) issues at jboss.org
Fri Jul 4 00:41:24 EDT 2014


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

Brett Meyer commented on SRAMP-474:
-----------------------------------

[~eric.wittmann], up for reviewing https://github.com/Governance/s-ramp/pull/449 and make sure it's what you had in mind?  If the log file is enabled, AbstractShellCommandReader simply writes each line.  That's the 2nd commit.  The first was me encapsulating all sramp.sh arguments in a class, including #properties and the new log-to-file option.

> CLI: Add a log-to-file option
> -----------------------------
>
>                 Key: SRAMP-474
>                 URL: https://issues.jboss.org/browse/SRAMP-474
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Shell
>            Reporter: Eric Wittmann
>            Assignee: Brett Meyer
>             Fix For: 0.6.0
>
>
> Currently CLI batch files must be created by hand.  This isn't too much of a hardship, but it might be convenient for the interactive console to help out with this by allowing the user to log all commands executed to a file.  This could be the basis for a CLI batch file that the user could include in some sort of integration scenario.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the overlord-issues mailing list