[forge-dev] Tricky situation with JavaParser and workspace resolution - need ideas.

[Lincoln Baxter, III]

https://issues.jboss.org/browse/FORGE-424

Right now, Forge's JavaParser is completely unaware of wildcard imports, as
stated in this issue:

The JavaParser Annotation.getQualifiedName() will return "Column" instead
of "javax.persistence.Column" for the following example class scenario (see
issue). It should be able to understand the wildcard, given the proper
metadata

In order to solve this, we are likely going to need to add a class resolver
extension that will allow us to encapsulate the dirty work of actually
loading JAR files from the project, loading other sources in the project,
and attempting to resolve the proper qualified name through java reflection:

for( String wildcard : wildcards )
{
   Class.forName( wildcard + simpleClassName);
}

If anyone has any brilliant ideas or inspiration around this issue, we
would love to hear them.

Thanks!
-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120110/5c021cec/attachment.html