[
http://jira.codehaus.org/browse/QDOX-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170980#action_170980
]
Robert Scholte commented on QDOX-152:
-------------------------------------
Leonardo was able to give some steps how to reproduce this issue.
After some digging I discovered this behaviour was introduced with rev-528, a
patch for QDOX-125
http://fisheye.codehaus.org/changelog/qdox/trunk?cs=528
It's not yet clear to me how the myfaces-build-plugin uses Qdox and why it
triggers this issue. So some help for a proper test would be nice.
(Visible to jira-users group)
> JavaClass.getFullyQualifiedName() does not work on version 1.9 (version 1.6.3
> works without problem). Manual resolve scanning imports are required
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QDOX-152
> URL: http://jira.codehaus.org/browse/QDOX-152
> Project: QDox
> Issue Type: Bug
> Components: Java API
> Affects Versions: 1.9
> Reporter: Leonardo Uribe
> Priority: Blocker
>
> Hi
> I'm trying to upgrade qdox version from 1.6.3 to 1.9 for
> myfaces-builder-plugin project.
> On version 1.6.3, JavaClass.getFullyQualifiedName() returns the fully
> qualified name no matter if the class is part of scanning path or not.
> On version 1.9, suppose a class (source file) that we are scanning, and the
> parent class is just a class in other jar, the package is omitted and just
> the class name is returned. I have to scan the imports of the source file to
> retrieve the "fully qualified name"!!!.
> At first view, this issue is blocker, because a previous version has a
> correct behavior and this version do not, so if the previous version behavior
> is correct there is no way to release this library again without solve this
> issue.
> For now, I'll change the code to scan imports if it is required (because some
> bugs on 1.6.3 that makes this plugin fail on some conditions are worst than
> this, and I don't know when could be released this library!).
--
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
