You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org> on 2009/07/14 06:59:22 UTC

[jira] Created: (MRM-1216) Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle

Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle
-----------------------------------------------------------

                 Key: MRM-1216
                 URL: http://jira.codehaus.org/browse/MRM-1216
             Project: Archiva
          Issue Type: Task
    Affects Versions: 1.2.1
            Reporter: Maria Catherine Tan
            Priority: Minor


This makes it possible to reconfigure the output which can not be done with the simple provider.

The properties that could then be set:
http://www.exampledepot.com/egs/java.util.logging/Props.html


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MRM-1216) Logging conflict on startup in Jetty bundle

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1216:
------------------------------

    Summary: Logging conflict on startup in Jetty bundle  (was: Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle)

changing summary to match

> Logging conflict on startup in Jetty bundle
> -------------------------------------------
>
>                 Key: MRM-1216
>                 URL: http://jira.codehaus.org/browse/MRM-1216
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 1.2.1
>            Reporter: Maria Catherine Tan
>            Assignee: Brett Porter
>            Priority: Minor
>
> This makes it possible to reconfigure the output which can not be done with the simple provider.
> The properties that could then be set:
> http://www.exampledepot.com/egs/java.util.logging/Props.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Assigned: (MRM-1216) Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter reassigned MRM-1216:
---------------------------------

    Assignee: Brett Porter

> Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle
> -----------------------------------------------------------
>
>                 Key: MRM-1216
>                 URL: http://jira.codehaus.org/browse/MRM-1216
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 1.2.1
>            Reporter: Maria Catherine Tan
>            Assignee: Brett Porter
>            Priority: Minor
>
> This makes it possible to reconfigure the output which can not be done with the simple provider.
> The properties that could then be set:
> http://www.exampledepot.com/egs/java.util.logging/Props.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MRM-1216) Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183625#action_183625 ] 

Brett Porter commented on MRM-1216:
-----------------------------------

more importantly, there is a bug in the way logging is done right now.

a number of classes bind to the slf4j from the jetty bundle instead of the one in the web application itself. Because the level is generally low enough we don't notice, but under debug (and during startup) they go to the wrong file.

> Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle
> -----------------------------------------------------------
>
>                 Key: MRM-1216
>                 URL: http://jira.codehaus.org/browse/MRM-1216
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 1.2.1
>            Reporter: Maria Catherine Tan
>            Priority: Minor
>
> This makes it possible to reconfigure the output which can not be done with the simple provider.
> The properties that could then be set:
> http://www.exampledepot.com/egs/java.util.logging/Props.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MRM-1216) Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183697#action_183697 ] 

Brett Porter commented on MRM-1216:
-----------------------------------

this is due to the use of commons-logging in both the jetty bundle and the application. The only alternative I can find is to remove jcl-over-slf4j from the jetty bundle, which requires switching to JSP 2.1

> Switch from slf4j-simple to slf4j-jdk14 in the jetty bundle
> -----------------------------------------------------------
>
>                 Key: MRM-1216
>                 URL: http://jira.codehaus.org/browse/MRM-1216
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 1.2.1
>            Reporter: Maria Catherine Tan
>            Assignee: Brett Porter
>            Priority: Minor
>
> This makes it possible to reconfigure the output which can not be done with the simple provider.
> The properties that could then be set:
> http://www.exampledepot.com/egs/java.util.logging/Props.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MRM-1216) Logging conflict on startup in Jetty bundle

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-1216.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.2

> Logging conflict on startup in Jetty bundle
> -------------------------------------------
>
>                 Key: MRM-1216
>                 URL: http://jira.codehaus.org/browse/MRM-1216
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 1.2.1
>            Reporter: Maria Catherine Tan
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.2.2
>
>
> This makes it possible to reconfigure the output which can not be done with the simple provider.
> The properties that could then be set:
> http://www.exampledepot.com/egs/java.util.logging/Props.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MRM-1216) Logging conflict on startup in Jetty bundle

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183706#action_183706 ] 

Brett Porter commented on MRM-1216:
-----------------------------------

solution:
- remove jetty-logging.xml and let everything go to stdout, which will be handled by wrapper
- remove slf4j and jcl-over-slf4j from jetty lib directory so that logs correctly go to webapp

> Logging conflict on startup in Jetty bundle
> -------------------------------------------
>
>                 Key: MRM-1216
>                 URL: http://jira.codehaus.org/browse/MRM-1216
>             Project: Archiva
>          Issue Type: Task
>    Affects Versions: 1.2.1
>            Reporter: Maria Catherine Tan
>            Assignee: Brett Porter
>            Priority: Minor
>
> This makes it possible to reconfigure the output which can not be done with the simple provider.
> The properties that could then be set:
> http://www.exampledepot.com/egs/java.util.logging/Props.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira