Jason has done an exhaustive search
of WTP and adopters, and has found no breakage. Last year
the two competing operation frameworks were combined, and these methods
but never used externally. After
some additional internal changes for the defects listed below, the need
for these methods is gone.
What should be our strategy?
Jason can provide more detail of this
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Phone: 919-254-1848 (T/L: 444)
----- Forwarded by Chuck
Bridgham/Raleigh/IBM on 03/29/2006 11:20 AM -----
Jason A Sholl/Raleigh/IBM@IBMUS Sent by: wtp-dev-bounces@xxxxxxxxxxx
03/28/2006 04:37 PM
Please respond to
"General discussion of project-wide or architectural issues."
[wtp-dev] IDataModel framework
If you are not using the IDataModel framework, then there is no need to
continue reading this note.
In order to fix bugs https://bugs.eclipse.org/bugs/show_bug.cgi?id=125338
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=118853, some api changes
are necessary. Though these changes are potentially breaking, I don't
believe there was any usage outside the internal classes I have already
cleaned up. If there are no objections, I would like to put these
changes in this week's integration build.
The following methods will be removed from the public API, because they
no longer make sense:
I did not find any references to any of the deleted classes or methods
anywhere in WTP. Lastly, I ran the api tool and am following up with
the owners to determine whether they are legitimate concerns. If
anyone has concerns about these changes please let me know.
Jason A. Sholl
919-543-0011 (t/l 441-0011)_______________________________________________
wtp-dev mailing list