And .... Should be in a format that allows one to manually generate a migration script for a new version of a third party library that didn't come with a migration script.
-- Mark -----Original Message----- From: Jacques Morel [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 11:02a To: [EMAIL PROTECTED] Subject: RE: [Eap-features] Refactoring of public APIs - Saving refaction in batch file Yes it is part of it. However it only supports package and class renaming and it is separated from the refactoring that the tool supports. This is a good tool for already formalized Migration like the swing repackaging. We need a similar feature that will allow the formulation of the Migration incrementally based on the refactoring applied to the project or a subproject. The list of "Migrations" would be automatically populated by all relevant refactorings (Rename package, Move class, Rename methods,...) applied on a potential subset of the sources. It could be saved to a file that could be distributed to users and reapplied on their sources. -----Original Message----- From: Brian Majewski [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 12:42 PM To: [EMAIL PROTECTED] Subject: RE: [Eap-features] Refactoring of public APIs - Saving refaction in batch file Have you looked at Tools | Migrate? Brian Majewski Systems Architect Chrome Systems Corporation [EMAIL PROTECTED] PHONE: +1-503-963-6410 / +1-800-936-8906 FAX: +1-503-963-6312 www.chrome.com Notice: This e-mail transmission and/or the attachments accompanying it may contain confidential information belonging to the sender or Chrome Systems Corporation. The information is only for the use of the intended recipient. If you have received this transmission in error, please notify the sender immediately by reply e-mail, and then destroy all copies of the transmission. -----Original Message----- From: Jacques Morel [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 24, 2002 9:46 AM To: [EMAIL PROTECTED] Subject: [Eap-features] Refactoring of public APIs - Saving refaction in batch file When your development team is divided in groups that owns different components and these components interact through public APIs, refactoring the APIs might require multiple-steps. Ideally everybody would own the code so if you rename an API method you can rename all its usages whether they are owned by you or not. However when you do not have control over all user components the current refactoring tool doesn't help. You need to save your refactoring into a refactoring batch file that can be applied to user components when they migrate to your new release. You can then release the refactoring file with the new interface. Users can apply the refactorings on their code. Jacques Morel _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
