[forge-issues] [JBoss JIRA] (ROASTER-10) Auto generated imports when a field type is set causes .java file to not compile.
[
https://issues.jboss.org/browse/ROASTER-10?page=com.atlassian.jira.plugin...
]
Antoine Lefebvre commented on ROASTER-10:
-----------------------------------------
I also got an issue when trying to create a wrapper class that encapsulate a class of the
same name.
Example:
{code:java}
package myPackage;
import anotherPackage.myClass;
public class myClass()
{
private myClass _myclass; // this is wrong it is should use the FQN i.e.
anotherPackage.myClass
}
{code}
Auto generated imports when a field type is set causes .java file to
not compile.
---------------------------------------------------------------------------------
Key: ROASTER-10
URL: https://issues.jboss.org/browse/ROASTER-10
Project: Roaster
Issue Type: Bug
Components: API
Affects Versions: 2.2.0.Final
Reporter: Walter Medvedeo
Fix For: 2.x Future
When we set the Type for a given field using the FieldSource.setType( X ) methods an
import is generated automatically.
Under some situations it causes the resulting class to not compile and it's not
posible to fix it using the api.
In order to avoid this, and also to be able to modify a given class in a more "safe
or controlled" way (for example in cases when we don't want to manage complex
refactorings or controlling imports), It's desirable to have setType( X, boolean
addImports) method that just change the field type to the provided type name and don't
add imports.
e.g:
Given the following declaration:
private org.test.Class1 myField;
myField.setType("org.somepackage.Class2", false)
will produce the following result:
private org.somepackage.Class2 myField;
and:
myField.setType("Class2", false)
will produce the following result:
private Class2 myField.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)