[forge-issues] [JBoss JIRA] Updated: (SEAMFORGE-328) Wrong import if imported class is a nested class
[
https://issues.jboss.org/browse/SEAMFORGE-328?page=com.atlassian.jira.plu...
]
Kevin Pollet updated SEAMFORGE-328:
-----------------------------------
Description:
For example, if we have the following classes:
{code}
public class A {
public static class B {
}
}
{code}
The import {{com.example.foo.A$B}} is added for the class B instead of
{{com.example.foo.A.B}}. It's because {{AbstractJavaSource#addImport(Class<?>
type)}} uses {{type.getName()}} to create the import, which returns
{{com.example.foo.A$B}}.
was:
For example, if we have these classes
{code}
public class A {
public static class B {
}
}
{code}
The following import is added for the class B, {{com.example.foo.A$B}} instead of
{{com.example.foo.A.B}}. It's because {{AbstractJavaSource#addImport(Class<?>
type)}} uses {{type.getName()}} to create the import which returns
{{com.example.foo.A$B}}.
Wrong import if imported class is a nested class
------------------------------------------------
Key: SEAMFORGE-328
URL: https://issues.jboss.org/browse/SEAMFORGE-328
Project: Seam Forge
Issue Type: Bug
Components: Parsers / File Manipulation
Affects Versions: 1.0.0.Beta2
Reporter: Kevin Pollet
For example, if we have the following classes:
{code}
public class A {
public static class B {
}
}
{code}
The import {{com.example.foo.A$B}} is added for the class B instead of
{{com.example.foo.A.B}}. It's because {{AbstractJavaSource#addImport(Class<?>
type)}} uses {{type.getName()}} to create the import, which returns
{{com.example.foo.A$B}}.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira