The Acceleo development team does its best to maintain downward compatibility towards Ganymede (Eclipse 3.4). Following is the compatibility chart (Note that there has been no "0.9" version, and Acceleo jumped right up to version 3.0 when graduating, details here) :
|Acceleo||Eclipse 3.4 - EMF 2.4||Eclipse 3.5 - EMF 2.5||Eclipse 3.6 - EMF 2.6||Eclipse 3.7 - EMF 2.7|
An empty cell indicates that the compatibility hasn't been tested for a particular combination.
Behavioral changes between versions
Take note that as new OCL features are enabled in new Eclipse versions, they allow shortcuts or characters in OCL expressions that cause Acceleo templates written within a newer Eclipse to be incompatible (at compilation time) with older Eclipses! In short, modules that compile in a given Eclipse will always compile in subsequent releases, and modules that have been compiled (whatever the version) should be launch-able in any Eclipse.
- Galileo allows us to properly check the return type of standard library operations; thus "oclAsType" calls that were mandatory in Ganymede aren't in Galileo. Templates making use of this cannot compile within Eclipse 3.4 without re-adding these calls.
- OCL 1.3 allowed us to activate an option to activate control characters within Acceleo templates. \n, \t, \r, \', \" and \\ can be used in templates to generate linefeeds, horizontal tabs, carriage returns, ... from Acceleo 3.0 onward. templates containing such characters will generate the text \n instead of linefeeds in Acceleo < 3.0.
|Project||Project · Installation · New & noteworthy · Release review · API policy · Retention policy · Next · Checklist|
|Features||Acceleo Features · Runtime · Acceleo editor · Views & Perspective · Debugger · Profiler · Traceability · Wishlist · Interpreter · Maven|
|User documentation||Getting Started · Acceleo operations reference · OCL operations reference · Text Production Rules · Migration From Acceleo 2.x · Best Practices · Videos · FAQ|
|Developer documentation||Source code · How to contribute · Compatibility · MOFM2T specification · OCL specification|
|Community||Blogs · Professional Support · Report a bug|