| Re: [imp-dev] move method refactoring problem...kindly help urgently.. |
| Hi there, This question is probably better asked on one of the eclipse.org newsgroups (e.g. eclipse.tools.jdt). And honestly, I'd like to be more helpful, but it's a bit hard to say what's going wrong in your code, given that you're passing null in various places for things that obviously need proper values. Also, you're using several JDT internal classes in your code, which is definitely not the right way to go. Finally, I'm not entirely sure what you're intending to do: - Are you trying to implement a new refactoring? If so, see here for a good article that should get you started: http://www.eclipse.org/articles/article.php?file=Article-Unleashing-the-Power-of-Refactoring/index.html . - Are you trying to implement support for the Move refactoring for a new language? I honestly haven't looked into this myself much, but the Move refactoring as implemented by the LTK supports "refactoring participants". See the class MoveParticipant for more info. - Are you simply trying to invoke a Move refactoring programmatically? If the latter, look in the archives of the eclipse.tools.jdt newsgroup for a response by Martin Aeschlimann dated 8 Oct 2007 and titled "Re: Move refactoring via descriptors". There's a code snippet in there that has been deemed by the JDT team to be the appropriate way to initiate Move refactorings. On Feb 24, 2010, at 7:45 AM, lehmia kiran wrote: Hi, <snip> -- Cheers, - Bob ------------------------------------------------- Robert M. Fuhrer Research Staff Member Programming Technologies Dept. IBM T.J. Watson Research Center IMP Project Lead (http://www.eclipse.org/imp) X10: Productivity for High-Performance Parallel Programming (http://x10-lang.org) |