Eclipse Community Forums: TMF (Xtext) » [SOLVED] Confirming new renaming infracture is not for Xbase languages

Help

Home

Home » Modeling » TMF (Xtext) » [SOLVED] Confirming new renaming infracture is not for Xbase languages

Show: Today's Messages :: Show Polls :: Message Navigator

[SOLVED] Confirming new renaming infracture is not for Xbase languages [message #1781192]

Fri, 02 February 2018 12:11

Stéphane Galland

Messages: 123
Registered: July 2014
Location: Belfort, France

Senior Member

Dear all.

According to the change log of Xtext 2.13, a new renaming infrastructure is provided, based on IChangeSerializer.

In the documentation of the MWE2 RefactorElementNameFragment2 fragment related to useChangeSerializer, it mentionned:

Use the newer rename infrastructure based on the change serializer also in Eclipse.
This is only applicable for non-Xbase languages.

The change log does not specify the "non-Xbase" constraint.

I would like to be sure that the new infrastructure cannot be used for my language, which uses the XExpression from Xbase, before starting to migrate to this new infrastructure.

Thank you by advance.

All the best.
Stéphane.

[Updated on: Fri, 02 February 2018 12:29]

Report message to a moderator