[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jdt-ui-dev] FW: [eclipse-dev] Planning Meeting Notes - Dec 21, 2005
|
So here’s a slightly whacky idea
that this enables (or maybe it has already been considered?). When
shipping breaking API changes, additional JDT tool support could allow the API
provider to capture the script generated by the API refactoring and package it
with the source JAR or feature. Then the API consumer could get a Quick
Fix option to apply the refactoring script to migrate to the new API.
This could make improving APIs easier by lowering the bar for things like
renames.
Mik
From:
eclipse-dev-bounces@xxxxxxxxxxx [mailto:eclipse-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Wilson
Sent: December 20, 2005 3:19 PM
To: eclipse-dev@xxxxxxxxxxx
Subject: [eclipse-dev] Planning
Meeting Notes - Dec 21, 2005
JDT UI:
...
-
refactoring:
-
refactoring history is now displayed in project property page and
can be exported as script
-
added Refactor->Apply Refactorings... action which executes
refactorings from a script
...
|
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
