[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1179) jboss-remoting.jar should log a version message when it is loaded

Ron Sigal (JIRA) jira-events at lists.jboss.org
Sat Feb 20 14:59:10 EST 2010


     [ https://jira.jboss.org/jira/browse/JBREM-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBREM-1179.
----------------------------

    Resolution: Done


Seeing the version every time Remoting gets used is annoying, so it would be nice to log the version at DEBUG level instead of using System.out.  On the other hand, using a logger requires using a classpath when running

  java -jar jboss-remoting.jar

which would be new and unpleasant.

The solution is to try to load the logger class using reflection.  If the logger class is available, the version gets logged at DEBUG level, and if a logger isn't available, no version is emitted.  In particular, the version gets logged in the context of the Application Server.

The change has been applied to branches 2.2 and 2.x.

> jboss-remoting.jar should log a version message when it is loaded
> -----------------------------------------------------------------
>
>                 Key: JBREM-1179
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1179
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>            Priority: Minor
>             Fix For: 2.2.3.SP2, 2.5.2.SP3 (Flounder)
>
>
> The logging should be done at DEBUG level.

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

        


More information about the jboss-remoting-issues mailing list