You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2011/01/07 13:23:50 UTC

[jira] Created: (KARAF-359) Add log:stash command

Add log:stash command
---------------------

                 Key: KARAF-359
                 URL: https://issues.apache.org/jira/browse/KARAF-359
             Project: Karaf
          Issue Type: New Feature
          Components: console
            Reporter: Andreas Pieber
             Fix For: 2.2.0


When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display

Something like

{code}
log:stash
// DO ACTION HERE
log:display (shows all the log happend between the last log:stash and the time I do log:display)
log:stash clear (remove the marker set by log:stash)
{code}

IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] [Updated] (KARAF-359) Add log:stash command

Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear updated KARAF-359:
---------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.0.1
    
> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>            Reporter: Andreas Pieber
>            Priority: Trivial
>             Fix For: 3.0.1, 3.1.0
>
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

--
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] [Commented] (KARAF-359) Add log:stash command

Posted by "Reuben Garrett (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277048#comment-13277048 ] 

Reuben Garrett commented on KARAF-359:
--------------------------------------

http://semver.org/
what a great way to structure version numbers!  thank you for the reference.  
                
> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>            Reporter: Andreas Pieber
>            Priority: Trivial
>             Fix For: 3.1.0
>
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

--
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] [Commented] (KARAF-359) Add log:stash command

Posted by "Michael Van Geertruy (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020155#comment-13020155 ] 

Michael Van Geertruy commented on KARAF-359:
--------------------------------------------

This is just a work-around, but you may try connecting to your Karaf instance with a client, and then (using the 3.0.0 version of log:display) type log:display <package-name> right before you do your thing on your karaf console.  This will allow you to view only those items affecting the package you are testing.

> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: console
>            Reporter: Andreas Pieber
>            Priority: Trivial
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (KARAF-359) Add log:stash command

Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Pieber updated KARAF-359:
---------------------------------

         Priority: Trivial  (was: Major)
    Fix Version/s:     (was: 2.2.0)

Yes, log:clear does the job (mostly), but the difference to log:stash would be that log:stash affects the -n param of log:display. Limiting it to the number of log-statements between stash and stash clear which can be above the e.g. default 500 line limit.

> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: console
>            Reporter: Andreas Pieber
>            Priority: Trivial
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] [Updated] (KARAF-359) Add log:stash command

Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Pieber updated KARAF-359:
---------------------------------

    Fix Version/s:     (was: 3.0.1)

According to semvers.org no non-bug-fixes should be handled on micro release branches
                
> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>            Reporter: Andreas Pieber
>            Priority: Trivial
>             Fix For: 3.1.0
>
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

--
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] [Updated] (KARAF-359) Add log:stash command

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-359:
---------------------------------------

    Fix Version/s: 3.1.0
                   3.0.0

> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: console
>            Reporter: Andreas Pieber
>            Priority: Trivial
>             Fix For: 3.0.0, 3.1.0
>
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] Commented: (KARAF-359) Add log:stash command

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/KARAF-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978760#action_12978760 ] 

Guillaume Nodet commented on KARAF-359:
---------------------------------------

I usually do the following:

> log:clear ; another action ; log display

It's usually sufficient for my needs.

> Add log:stash command
> ---------------------
>
>                 Key: KARAF-359
>                 URL: https://issues.apache.org/jira/browse/KARAF-359
>             Project: Karaf
>          Issue Type: New Feature
>          Components: console
>            Reporter: Andreas Pieber
>             Fix For: 2.2.0
>
>
> When I trace down a problem I make extensive use of log:display. Basically it works really great, but sometimes I would wish to see only the log between my latest action and the next log:display
> Something like
> {code}
> log:stash
> // DO ACTION HERE
> log:display (shows all the log happend between the last log:stash and the time I do log:display)
> log:stash clear (remove the marker set by log:stash)
> {code}
> IMHO we could use the syntax of git stash here mostly. Named stashes could be an extension to this feature but I don't think it's required.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.