One thing that may be needed is a someone to look at where we are using internal APIs and identify whether a suitable public API is available. Would it be worth creating a bug entry to track this task?
Andre On 8-Nov-06, at 16:36 , Doug Schaefer wrote: O.K. I’ve timed out. The patch has been committed. On your next update from HEAD, you will need to build against Eclipse 3.3 M3. I’ve been using this combination for a couple of days now and haven’t noticed anything bad. From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants Sent: Tuesday, November 07, 2006 4:55 AM To: CDT General developers list. Subject: RE: [cdt-dev] Ready for M3 yet? Doug, The usage of the provisional and internal API in this particular case has been discussed and approved by the community. And, please, let me review the patch first. Regards, Mikhail K. From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Sent: 06 November 2006 21:03 To: CDT General developers list. Subject: RE: [cdt-dev] Ready for M3 yet? BTW, it is our punishment for using internal APIs. As long as we continue to do that we will not be able to support old Eclipse platform releases. From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Sent: Monday, November 06, 2006 3:59 PM To: CDT General developers list. Subject: RE: [cdt-dev] Ready for M3 yet? Why? There is no intention for CDT 4.0 to support running on Eclipse 3.2. Now is as good a time as any to drop it. From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin Sent: Monday, November 06, 2006 3:42 PM To: CDT General developers list. Subject: Re: [cdt-dev] Ready for M3 yet? Please don't break 3.2 compatibility yet. Could you please describe the problem and solicit feedback from more people before declaring a solution supporting both 3.3 and 3.2 impossible. -sergey -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ cdt-dev mailing list |