RE: [cdt-dev] CDT 2.0 M5 and Eclipse compatibility

[Sebastien Marineau <sebastien@xxxxxxx>]

I vote for a break with the 2.x stream and moving to 3.0 -- the faster
we get on the 3.0 stream, the sooner we can change the CDT UI to 
use the 3.0 features and look.

Sebastien

> 
> Well, I didn't get much response from anyone other than our 
> friend Ed. So, 
> sitting around today, I have managed to get CDT 2.0 up and 
> running on the 
> latest Eclipse 3.0 nightly build. The fine people of the 
> Eclipse Platform 
> have added some utilities that quickly convert plugins to 
> make up for the 
> Eclipse platform changes. This works especially using PDE containers 
> (which I notice are working well in 2.1.2 but still have 
> issues in 3.0). I 
> then ran into an API change where openEditor now requires the 
> extension id 
> of the editor you want. Luckily there's a utility to find the default 
> editor for a given filename. Plus I ran into the usual use of 
> internal 
> interfaces which disappeared but have good alternatives. All 
> API change 
> effects were to org.eclipse.cdt.ui and I have attached a patch.
> 
> All in all, I was able to create a new project, create a new 
> class with 
> the new class wizard, and debug with stop on main. I couldn't get 
> breakpoints to work. This was all with mingw.
> 
> In the end the changes weren't that bad but they do break 
> compatibility 
> with 2.1.x.
> 
> So, do we go for it? Get on to 3.0 now. Or wait?
> 
> I vote go now. We have a ton of work to get the CDT working 
> nicely on 3.0. 
> The sooner we start the better. Plus the latest 3.0 build seems to be 
> pretty stable despite the major changes to the platform.
> 
> 
> 
> Cheers,
> Doug Schaefer, Senior Software Developer
> IBM Rational Software, Ottawa, Ontario, Canada
> 
> 
> 
> Douglas Schaefer/Ottawa/IBM@IBMCA 
> Sent by: cdt-dev-admin@xxxxxxxxxxx
> 11/13/2003 09:59 AM
> Please respond to
> cdt-dev
> 
> 
> To
> cdt-dev@xxxxxxxxxxx
> cc
> 
> Subject
> RE: [cdt-dev] CDT 2.0 M5 and Eclipse compatibility
> 
> 
> 
> 
> 
> 
> Good point, Ed,
> 
> This is certainly the objective (and why we are actually 
> using the same 
> milestone numbers). And right now, CDT Head and the CDT 2.0M5 
> will run 
> with Eclipse 3.0M4. There has been a lot of API and plugin 
> changes to 3.0 
> with the Rich Client Platform work and we just haven't got around to 
> keeping up and simply aren't going to be ready by the end of 
> next week. 
> What this milestone for the CDT will give us is a number of 
> important bug 
> fixes and compatibility with the Eclipse 3.0M4 build.
> 
> I'm also sure we're not the only component also going through 
> this. This 
> is going to be the roughest point in the cycle for Eclipse 
> 3.0 adoption 
> for everyone. It will take time. Once the API changes slow 
> down, it'll be 
> a lot easier to keep in sync.
> 
> Cheers,
> Doug Schaefer, Senior Software Developer
> IBM Rational Software, Ottawa, Ontario, Canada
> 
> 
> 
> "Ed Burnette" <Ed.Burnette@xxxxxxx> 
> Sent by: cdt-dev-admin@xxxxxxxxxxx
> 11/13/2003 09:42 AM
> Please respond to
> cdt-dev
> 
> 
> To
> <cdt-dev@xxxxxxxxxxx>
> cc
> 
> Subject
> RE: [cdt-dev] CDT 2.0 M5 and Eclipse compatibility
> 
> 
> 
> 
> 
> 
> I have a whole bunch of users who are just itching to use CDT again 
> (myself included) but can't because of the delays getting 3.0 
> supported. 
> Please reconsider tying the CDT builds directly with the 
> Platform builds 
> and making CDT run on the very latest 3.0 streams. We have to 
> use those 
> latest 3.0 streams for reasons I won't go into now and it's very 
> frustrating when CDT won't work with it.
> 
> I would recommend a simple rule: CDT HEAD should work with 
> Platform HEAD, 
> with continuous integration. Does anyone else feel the same way?
> --Ed
> 
> > -----Original Message-----
> > From: Douglas Schaefer [mailto:dschaefe@xxxxxxxxxx] 
> > Sent: Wednesday, November 12, 2003 9:41 PM
> > To: cdt-dev@xxxxxxxxxxx
> > Subject: [cdt-dev] CDT 2.0 M5 and Eclipse compatibility
> > 
> > ...I would recommend that we stay with 2.1.x compatibility for this 
> > milestone so that we have a stable snapshot of CDT 2.0 that 
> people could 
> 
> work 
> > with. After this is release, we should then immediately begin the 
> > migration to 3.0 to get this work under way.
> > 
> > Thoughts?
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
>