Community
Participate
Working Groups
Bug 350862 reports an Xtext API breakage for Xtext 2.0.1. This breaks the 3.2.1 build. Since the breakage affects only renaming code that doesn't work anyway, comment out that code for now.
Correction: Xtext Bug 354082
Problem code commented out in maintenance/R3_1. Should we leave this commented out permanently or, should be revert once Xtext fixes to preserve compatibility in a very very obscure area? I think it can only affect a derived OCL user who has chosen to override the OCLsdlib renaming to make it work. Since the code was only available for override just before Indigo, and there are very very few OCLstdlib users, it seems very very very unlikely that anyone will notice.
Xtext 2.0.1 is already released so that changes the balance of practicality. Eliminating the non-functional refactoring support should avoid far more problems than it risks.
CLOSED after a year in the RESOLVED state.