[
https://issues.apache.org/jira/browse/SCM-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964572#comment-17964572
]
Olivier Lamy commented on SCM-411:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#635|https://github.com/apache/maven-scm/issues/635].
> Performance: logger calls are not optimal
> -----------------------------------------
>
> Key: SCM-411
> URL: https://issues.apache.org/jira/browse/SCM-411
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: 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
> Affects Versions: 1.1
> Reporter: Siveton Vincent
> Assignee: Siveton Vincent
> Priority: Major
> Fix For: 1.2
>
>
> Several logger calls are getLogger().debug()
> Should be replace by:
> {noformat}
> if ( getLogger().isDebugEnabled() )
> {
> getLogger().debug( ... );
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
