[ https://jira.jboss.org/jira/browse/JBREM-1179?page=com.atlassian.jira.plu... ] Ron Sigal closed JBREM-1179. ---------------------------- Resolution: Done When jboss-remoting.jar is loaded, org.jboss.remoting.Version will print "Remoting version: ...". This change has been applied to branches 2.x. and 2.2. -- 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

[ https://jira.jboss.org/jira/browse/JBREM-1179?page=com.atlassian.jira.plu... ] 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. -- 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