You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/06/23 19:26:45 UTC

[jira] Created: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
---------------------------------------------------------------------------------------------

                 Key: TAPESTRY-2474
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
             Project: Tapestry
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.0.13
            Reporter: Howard M. Lewis Ship


It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2474:
-------------------------------------------

    Fix Version/s: 5.1

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>             Fix For: 5.1
>
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Filip S. Adamsen (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607812#action_12607812 ] 

Filip S. Adamsen commented on TAPESTRY-2474:
--------------------------------------------

Yeah, but for the 10% that don't use Log4J, it's very nice. I use Logback. :)

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Ceki Gulcu (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630668#action_12630668 ] 

Ceki Gulcu commented on TAPESTRY-2474:
--------------------------------------

Cool. First time I come across markers in an OSS project. I'd be interested in your comments about markers.

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.0.15
>
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: [jira] Closed: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
I'm very happy to see that this made it into 5.0 - thanks Howard! :)

-Filip

On 2008-09-11 20:45, Howard M. Lewis Ship (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Howard M. Lewis Ship closed TAPESTRY-2474.
> ------------------------------------------
> 
>        Resolution: Fixed
>     Fix Version/s:     (was: 5.1)
>                    5.0.15
> 
>> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
>> ---------------------------------------------------------------------------------------------
>>
>>                 Key: TAPESTRY-2474
>>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>>             Project: Tapestry
>>          Issue Type: Improvement
>>          Components: tapestry-core
>>    Affects Versions: 5.0.13
>>            Reporter: Howard M. Lewis Ship
>>            Assignee: Howard M. Lewis Ship
>>             Fix For: 5.0.15
>>
>>
>> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Closed: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-2474.
------------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 5.1)
                   5.0.15

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.0.15
>
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607795#action_12607795 ] 

Howard M. Lewis Ship commented on TAPESTRY-2474:
------------------------------------------------

... if Log4J supported the Markers, but Log4J (the implementation 90+% of people will use) just ignores Markers.

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Assigned: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAPESTRY-2474:
----------------------------------------------

    Assignee: Howard M. Lewis Ship

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1
>
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-2474) Define and use a standard set of SL4J Markers for logging, to make it easier to filter output

Posted by "Filip S. Adamsen (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607590#action_12607590 ] 

Filip S. Adamsen commented on TAPESTRY-2474:
--------------------------------------------

Oh yes! This would be very, very nice to have.

> Define and use a standard set of SL4J Markers for logging, to make it easier to filter output
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2474
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2474
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.13
>            Reporter: Howard M. Lewis Ship
>
> It would be nice if there were markers used by Tapestry to assist in filtering; for example, a Marker related to code generation and page constructor, a Marker for event notification tracing, etc.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org