I think the Eclipse guys (and girls, I'm sure) are a operating at a rather "higher" level in terms of what qualifies as a broken API. The Eclipse platform is friggin' HUGE, so while certain things break every release, in terms of the whole platform they're relatively minor.
It's also targeted at supporting major projects, which implies a slower adoption rate and pretty restrictive version requirements. CFEclipse is both small and rapidly developing, so I'd think it's outside the main focus of what Eclipse (the platform) is designed for. cheers, barneyb On 7/2/07, Sean Corfield <[EMAIL PROTECTED]> wrote: > On 7/2/07, Doug Arthur <[EMAIL PROTECTED]> wrote: > > Maybe the Eclipse guys should have called if 4.0 if it's that extensive of a > > change. > > So far pretty much every point release of Eclipse has broken a number > of plugins... I expect it'll will break the Flex Builder 2 / 3 plugins > as well as CFEclipse... > -- > Sean A Corfield -- (904) 302-SEAN > An Architect's View -- http://corfield.org/ -- Barney Boisvert [EMAIL PROTECTED] http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:282740 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
