OOPSLA

3rd Workshop on Refactoring Tools

• Cross Language Refactoring for Groovy and Java in Eclipse
  The Groovy Plug-in for the Eclipse IDE features a number of automated refactorings, that were realized in a bachelor thesis at HSR University of Applied Sci- ences, Rapperswil, Switzerland. Although Groovy and Java code can be used mutually in projects, the already implemented refactorings are limited to Groovy code.
  In a subsequent bachelor thesis the Groovy Eclipse Plug-in was extended with Cross-language Refactor- ings by the first two authors: If either a Groovy or a Java element is renamed, both languages are re- spected throughout the complete refactoring process. The achieved goal was to sup-port all possible rename actions, no matter in which language the element to be refactored was defined.
  As a result, the Groovy Eclipse Plug-in now offers a higher lever of integration with the Java Development Tools and more productivity for Groovy developers. Due to automated testing over complete development process, the solution is ready for production use and will be submitted to the official plug-in maintainers.

The Institute for Software is going to Nashville!

Tutorials:

• Green Bar for C++: Test Driven Development and Refactoring for C++
  A hands-on tutorial on how to employ TDD in C++.
  
  
• Understanding Security with Patterns
  Security Patterns give you the language and understanding to improve your security desgin, similar to how design patterns helped your OOAD.
  

Practitioners report:

• Retaining Comments when Refactoring Code
  Refactoring program code preserves its semantics, even while changing its structure. Program comments do not carry semantics, so by definition an automated refactoring tool can remove them to be formally correct. However, if carefully crafted formatting or comments disappear while refactoring code, developers will be unhappy. This report shows a method for comment retention that can be implemented using an extended AST to be used for more languages and IDEs.