commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary D. Gregory (JIRA)" <>
Subject [jira] [Created] (LANG-696) Deprecate ClassUtils getShortClassName in favor of Class getSimpleName
Date Thu, 21 Apr 2011 15:28:05 GMT
Deprecate ClassUtils getShortClassName in favor of Class getSimpleName

                 Key: LANG-696
             Project: Commons Lang
          Issue Type: New Feature
          Components: lang.*
    Affects Versions: 2.6
            Reporter: Gary D. Gregory
            Assignee: Gary D. Gregory
             Fix For: 3.0

Added two null-safe ClassUtils.getSimpleName() APIs.

---------- Forwarded message ----------
From: Gary Gregory <>
Date: Mon, Apr 11, 2011 at 10:18 AM
Subject: [Lang] ClassUtils getShortClassName != Class getSimpleName
To: Commons Developers List <>

Hi All:

Should we deprecate ClassUtils getShortClassName in favor of Class getSimpleName?

The behavior of getShortClassName is undocumented for arrays in the Javadoc and is different
from getSimpleName.

When I replace the guts of getShortClassName to call getSimpleName, one test fails:

junit.framework.ComparisonFailure: null expected:<[ToStringStyleTest.]Person[name=John
Q. ...> but was:<[]Person[name=John Q. ...>
    at junit.framework.Assert.assertEquals(
    at junit.framework.Assert.assertEquals(
    at org.apache.commons.lang3.builder.ShortPrefixToStringStyleTest.testPerson(

For now, I've made a note in the Javdoc to consider using getSimpleName.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message