Community
Participate
Working Groups
Example: ------- class foo { def bar() {} } ------- refactor "bar" to "foo" and refactoring will raise a warning "If you proceees, the method....... will have a constructor name". This validation is invalid, since in Xtend the constructors are named "new" and not like the class (as in Java).
This message comes frm JDT and is not essentially wrong: It will compile to a Java method that has a constructor name. This issue will be hidden, as we generate a @SuppressWarnings("all").
BTW, renaming a method to 'new' is also invalid which will be prompted by JDT: "'new' is not a valid identifier". Do you thing we need an additional Xtend based error message for this case?
I'd like to close this as * The issue arises only if people use either lowercase class names or uppercase method names. Who does so should be used to seeing lots of warnings... * The issue is there. It is just not on the Xtend but on the derived Java side. * It's only a warning, doesn't keep anyone from doing something. If anybody objects, please reopen.
