[SCM-411] Performance: logger calls are not optimal

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 1.2
• Component/s: maven-scm-api, maven-scm-provider-accurev, maven-scm-provider-bazaar, maven-scm-provider-clearcase, maven-scm-provider-cvs, maven-scm-provider-gitexe, maven-scm-provider-local, maven-scm-provider-mercurial (hg), maven-scm-provider-monotone, maven-scm-provider-perforce, maven-scm-provider-pvcs, maven-scm-provider-starteam, maven-scm-provider-svn, maven-scm-provider-synergy, maven-scm-provider-vss
• Assignee: Siveton Vincent
• Reporter: Siveton Vincent
• Created: 03/Sep/08 17:21
• Updated: 03/Sep/08 17:39
• Resolved: 03/Sep/08 17:39

Description

Several logger calls are getLogger().debug()
Should be replace by:

if ( getLogger().isDebugEnabled() )
{
    getLogger().debug( ... );
}