|Re: [eclipse-pmc] Add back an old method from 3.3 (detected as an API addition since 3.4M6a)|
ok, I admit that adding it with an empty body is not the best answer for existing callers if any. So the best answer would be to remove it completely and leave the version of JDT/Core as 3.4 with an entry in the porting guide. I don't like the consequence of removing it to increase the version of JDT/Core to 4.0. So would you approve this solution ? Olivier Mike Wilson/Ottawa/IBM@IBMCA Sent by: eclipse-pmc-bounces@xxxxxxxxxxx 2008-04-30 10:30 Please respond to eclipse-pmc@xxxxxxxxxxx To eclipse-pmc@xxxxxxxxxxx cc Subject Re: [eclipse-pmc] Add back an old method from 3.3 (detected as an API addition since 3.4M6a) This brings up an interesting discussion about how religiously we have to adhere to our API conventions. Somehow adding this method back, just to make the API tool happy, seems odd (particularly, since it doesn't work any more). Should we not just add an entry to the porting guide instead? McQ.
Back to the top