Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Xtext clients on the train

Hi Ed,

please don't hesitate to ask use for help if you face problems when migrating your Xtext based projects. Unfortunately it is not possible for us to maintain a semantically or source/bytecode compatible deprecation layer for the carefully decided but necessary changes from 1.0 to 2.0 (e.g. the one that you mentioned regarding the node model).

Please contact me in case there is anything that I or another Xtext committer can do (e.g. provide patches for your implementation) to help you migrate your projects.

Kind Regards,
Sebastian Zarnekow


On 17.01.2011, at 18:04, Ed Willink wrote:

Hi

The Xtext 2.0 changes make me very confused about what API compatibility means. Can someone clarify?

On the one hand, http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy , suggests that API removal takes a couple of releases. On the other hand, a major release is allowed to change API, and a change is potentially nastier to clients than a removal since there may be inadequate compiler/loader diagnosis.

In the particular case of Xtext, I think there may be a problem for the wider community.

(For MDT/OCL, the associated MDT/OCL code has significant changes so it can hopefully adapt to the new API without too much difficulty.)

However, Xtext has become very popular very rapidly and so there are many Eclipse users with Xtext 1.0 products. It seems undesirable that these are all broken in Indigo. The original developers can grumble and rebuild, but third party users are in trouble until redistribution from the developers occurs.

I suggest that now that Xtext 2.0 has established new more advanced APIs, that the old 1.0 APIs be reinstated. e.g. The new ILeafNode should extend a deprecated LeafNode interface that emulates the removed LeafNode. NodeUtil could be re-instated and deprecated with delegation to new methods. Since package paths have changed this should not be too difficult. This would enable 1.0 APIs to persist through perhaps Xtext 2.0, 2.1 and vanish in perhaps 3.0.

   Regards

       Ed Willink



On 17/01/2011 07:38, Sven Efftinge wrote:
Hi all,

for M5 we (Xtext) will promote the 2.0 stream to the indigo builds, which contains some API changes. We would like to help any clients updating/migrating their code and would kindly ask to inform us if you use Xtext somehow.

I know the Ecore Tools do and we are already in contact with Ed Willink.
Are there any other projects consuming Xtext?

Best Regards,
Sven

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3384 - Release Date: 01/16/11


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top