| Hi,
It’s not important for M1 but often with those renames it also means some work to keep workspace compatibility. Eclipse Platform guarantees workspace compatibility even on API breaks. There is no such policy (AFAIK) for non-platform projects but in my opinion workspace compatibility should be kept at the very least with the previous minor release so there is always an upgrade path.
So I guess my question is: is there an impact on workspace compatibility and if so is it addressed?
Thanks a lot,
Marc-André
Hi cdt-devers,
I would like to try to get this bundle reorg that Martin previously announced in M1 that was scheduled for today, but has a hard deadline of Wednesday. I have published the build for a provisional M1, but will replace it (assuming no objections) as soon as possible and make the formal announcement.
Thanks, Jonah Thank you Martin for publicising this to the whole community.
Jonah
Hi all,
while working on bug [564349], I realized that package /
org.eclipse.cdt.cmake.is.core.participant/ was inadvertently *not* marked as
experimental. The rename to /org.eclipse.cdt.cmake.jsoncdb.participant/ will
cause a breaking API change.
This change only affects CMake build, indexer support.
Third-party compiler vendors that provide a plugin teaching Eclipse CDT their
compiler specific command-line options will have to update the import
statements in their plugin's code. (Most likely there is none yet.)
Martin
[564349] https://bugs.eclipse.org/bugs/show_bug.cgi?id=564349
--
Cd wrttn wtht vwls s mch trsr.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
|
