[
http://jira.codehaus.org/browse/QDOX-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168202#action_168202
]
Robert Scholte edited comment on QDOX-152 at 3/6/09 11:28 AM:
--------------------------------------------------------------
Hi Leonardo,
while developing on QDOX-151 I ran into comparable issues around the full
qualified name. So maybe it's more efficient if you can apply a test, 'cause
there's a chance it's already fixed in my codebase.
found this test, which succeeds
{code:title=JavaDocBuilderTest.java|borderStyle=solid}
public void testBinaryClassesAreFound() throws Exception {
String in = ""
+ "package x;"
+ "import java.util.*;"
+ "class X {"
+ " ArrayList a();"
+ "}";
builder.addSource(new StringReader(in));
JavaClass cls = builder.getClassByName("x.X");
Type returnType = cls.getMethods()[0].getReturns();
JavaClass returnClass = builder.getClassByName(returnType.getValue());
assertEquals("java.util.ArrayList",
returnClass.getFullyQualifiedName());
}
{code}
was (Author: rfscholte):
Hi Leonardo,
while developing on QDOX-151 I ran into comparable issues around the full
qualified name. So maybe it's more efficient if you can apply a test, 'cause
there's a chance it's already fixed in my codebase.
> 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
