[editors] Accommodate Xtext 2.8 incompatibility

[eclipse-ocl-bot]

| --- | --- | | Bugzilla Link | 456506 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Jan 02, 2015 05:37 EDT | | Modified | May 26, 2015 04:40 EDT | | Reporter | Ed Willink |

Description

Xtext 2.8.0M4 makes breaking changes to generated package names: see Bug 456184.

For simple compatibility, we must therefore either never regenerate, or regenerate with Xtext < 2.8.0M4. Neither is practical in the long term.

Suggest that a new ocl.xtext.2_7 plugin with optional dependencies on xtext 2.3.0 inclusive to 2.8.0 exclusive provide only the required xtext.ide package declarations with delegations to xtext.ui. Perhaps we just rebadge xtext.ui 2.8.0 that has the required backward compatibility delegations anyway.

[eclipse-ocl-bot]

By Ed Willink on Feb 22, 2015 18:06

Introducing fake plugins/classes seems dangerous in the absence of a deep understanding of Guice binding resolution.

Much easier to just auto-edit as described in Bug 460552#c1.

Pushed to master.

Currently in use by the regenerated QVTd.

OCL editors not yet regenerated.

[eclipse-ocl-bot]

By Ed Willink on Feb 25, 2015 16:49

Xtext has reverted its breajkoing chnages so the Backporting edits are no longer necessary.

[eclipse-ocl-bot]

By Ed Willink on Feb 26, 2015 12:15

Bug 460661 summarises the fixes.