[
http://jira.codehaus.org/browse/QDOX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Hammant closed QDOX-179.
-----------------------------
> Annoying name difference between methods JavaClass.getFullyQualifiedName()
> and Type.getFullQualifiedName()
> ----------------------------------------------------------------------------------------------------------
>
> Key: QDOX-179
> URL: http://jira.codehaus.org/browse/QDOX-179
> Project: QDox
> Issue Type: Improvement
> Components: Java API
> Affects Versions: 1.10
> Reporter: Antti Karanta
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 1.10.1
>
>
> The method for getting the fully qualified name of a class is named slightly
> differently in JavaClass and Type
> JavaClass.getFullyQualifiedName()
> Type .getFullQualifiedName()
> Note the missing y in Type's version of the method.
> With Java you notice this easily at compile time (or may not notice it at all
> if you insert the method calls using e.g. Eclipse's method name completion),
> but with dynamic languages (e.g. Groovy and JRuby) it is annoying to have to
> remember each time which one to use.
> I suggest deprecating Type.getFullQualifiedName() and adding
> getFullyQualifiedName() there as the method name seems to have a typo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
