Refactoring support for class library migration Export

@inproceedings{citeulike:387535, abstract = {As object-oriented class libraries evolve, classes are occasionally deprecated in favor of others with roughly the same functionality. In Java's standard libraries, for example, class Hashtable has been superseded by HashMap, and Iterator is now preferred over Enumeration. Migrating client applications to use the new idioms is often desirable, but making the required changes to declarations and allocation sites can be quite labor-intensive. Moreover, migration becomes complicated---and sometimes impossible---if an application interacts with external components, if a legacy class is not completely equivalent to its replacement, or if multiple interdependent classes must be migrated simultaneously. We present an approach in which mappings between legacy classes and their replacements are specified by the programmer. Then, an analysis based on type constraints determines where declarations and allocation sites can be updated. The method was implemented in Eclipse, and evaluated on a number of Java applications. On average, our tool could migrate more than 90\% of the references to legacy classes.}, address = {New York, NY, USA}, author = {Balaban, Ittai and Tip, Frank and Fuhrer, Robert}, booktitle = {OOPSLA '05: Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications}, citeulike-article-id = {387535}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=1094832}, citeulike-linkout-1 = {http://dx.doi.org/10.1145/1094811.1094832}, doi = {10.1145/1094811.1094832}, isbn = {1-59593-031-0}, keywords = {apitrafo, refactoring}, location = {San Diego, CA, USA}, pages = {265--279}, posted-at = {2009-11-02 15:42:17}, priority = {2}, publisher = {ACM}, title = {Refactoring support for class library migration}, url = {http://dx.doi.org/10.1145/1094811.1094832}, year = {2005} }

TY - CONF ID - citeulike:387535 L3 - citeulike-article-id:387535 N2 - As object-oriented class libraries evolve, classes are occasionally deprecated in favor of others with roughly the same functionality. In Java's standard libraries, for example, class Hashtable has been superseded by HashMap, and Iterator is now preferred over Enumeration. Migrating client applications to use the new idioms is often desirable, but making the required changes to declarations and allocation sites can be quite labor-intensive. Moreover, migration becomes complicated---and sometimes impossible---if an application interacts with external components, if a legacy class is not completely equivalent to its replacement, or if multiple interdependent classes must be migrated simultaneously. We present an approach in which mappings between legacy classes and their replacements are specified by the programmer. Then, an analysis based on type constraints determines where declarations and allocation sites can be updated. The method was implemented in Eclipse, and evaluated on a number of Java applications. On average, our tool could migrate more than 90% of the references to legacy classes. CY - San Diego, CA, USA SN - 1-59593-031-0 AD - New York, NY, USA EP - 279 TI - Refactoring support for class library migration PB - ACM T2 - OOPSLA '05: Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications SP - 265 KW - apitrafo KW - refactoring AU - Balaban, Ittai AU - Tip, Frank AU - Fuhrer, Robert PY - 2005/// UR - http://dx.doi.org/10.1145/1094811.1094832 ER -