Xpand/New And Noteworthy
- 1 Xpand 2.2
- 2 Xpand 2.1
- 3 Xpand 2.0
- 4 Version 1.4.0
- 5 Version 1.3.0
- 6 Version 1.2.1 (Juno)
- 7 Version 1.1.0 (Indigo)
- 8 Version 1.0.0 (Helios)
- 9 Version 0.7.0 (Galileo)
Version 2.2 is a maintenance release with a small number of bugfixes. Main focus was on fixing the Xpand debugger feature.
Version 2.1 is a maintenance release with a small number of bugfixes.
New Feature: Builder Exclusion Patterns
On large projects Xpand's builder may consume much time when saving resources. There was the demand to specify patterns of resources that are explicitly excluded from the build. A preference page has been added which allows the specification of the exclusion patterns. Further, the existing preference pages have been refactored.
Version 2.0 is the first major release since Xpand's initial transition from former openArchitectureWare. Over the time, Xpand's codebase evolved with solution of numerous issues, while strong backward API compatibility was kept. Although this version is a major version increment, it is mainly a maintenance release. But the breaking API changes made it necessary to declare it as such. Though the release is not strictly backward compatible, large portions of the code are still backward compatible. See below breaking API changes for reference.
While we do our best to keep Xpand backward compatible to Eclipse Galileo (3.5), we cannot grant this compatibility to 100%. Xpand is built against Eclipse Juno (3.8). This is mainly caused by other frameworks Xpand is built against.
- EMF Compare 2.1 - Used by Xpand Incremental Feature
- MDT UML2 4.0 - Used by Xpand UML2 Typesystem Adapter
- CDT 5.4 - Used by Xpand CDT Support Feature
Software User Agreement & License Update
The Eclipse Software User Agreement (SUA) contained a broken link, which made it necessary for all projects participating in the Eclipse Luna Release Train to update distributed files. See 431255, 432806 for details. Additionally Xpand's license was upgraded to the current 2014 version.
- Class org.eclipse.internal.xtend.util.ProfileCollector removed. It was used by Xpand's MWE components (Generator, CheckComponent, XtendComponent).
- org.eclipse.internal.xtend.expression.ast.Identifier: toValue() was removed and replaced by toString().
- org.eclipse.xpand2.output.Outlet#shouldWrite(FileHandleImpl) replaced by org.eclipse.xpand2.output.Outlet#shouldWrite(FileHandle)
- org.eclipse.internal.xpand2.codeassist.XpandTokens removed, replaced by org.eclipse.internal.xpand2.XpandTokens
- org.eclipse.internal.xtend.type.impl.java.JavaBeansMetaModel removed, replaced by org.eclipse.xtend.type.impl.java.JavaBeansMetaModel
- org.eclipse.xtend.check.ui.editor.lang.CheckTokens removed, replaced by org.eclipse.xtend.ui.editor.lang.XtendTokens
- org.eclipse.xtend.typesystem.xsd.XMLMixedContentFormater removed, replaced by org.eclipse.xtend.typesystem.xsd.XMLMixedContentFormatter
- org.eclipse.internal.xtend.xtend.ast.ImportStatement removed, replaced by org.eclipse.internal.xtend.xtend.ast.ExtensionImportStatement
Xpand 2.0 was again optimized in regards of its execution performance (Bugzilla Report: Performance)
For a complete list of changes refer to: Bugzilla Report
Xpand 1.4.0 is a maintenance release. Main focus is bugfixing and minor API extension.
The API is kept backwards compatible. API changes are regarding new API or opened API.
- The main workflow components Generator, XtendComponent and CheckComponent have been refactored to allow easier customization. State accessed by the main methods checkConfigurationInternal() and invokeInternal2() is reachable also from subclasses now by either protected fields or accessor methods. (406653).
- The CDT support plugin org.eclipse.xpand.support.cdt is now build against CDT 5.4. There was usage of internal API of CDT 5.2, which was made public API with CDT 5.3. (406300, 390087)
Some methods and fields have been marked deprecated since they are planned for removal for 2.0. Affected classes are:
- When dependent resources are not existing, the resource caching in the UI does not work. This leads to performance downgrade during the analysis phase in the case that projects have this consistency error. The bug was introduced with release 1.3.0. (405165)
UI / Build
- Only the first Jar of included resources are recognized for Content Assist (407934)
- During the build ClassCastExceptions were thrown when EMF classes have properties with array types. (406765)
- QualifiedName creation for Windows paths (C:\...) failed (407101)
- The hyphen operator "-" in «ENDREM-» was ignored, the following newline was printed to the result. (405769)
Xpand 1.3.0 is a maintenance release. Main focus in this Xpand release is performance and memory optimization.
Performance and Memory Optimization
Xpand is used in large-scale projects, where overall performance is crucial. For the Kepler release Xpand has been intensively profiled to identify performance hot spots. Performance is meant in both execution performance as well as memory usage. Often the optimization on the one side reduces the performance on the other side: accelerating execution performance often uses caching, which increases memory usage, and vice-versa, reducing memory consumption requires more processing time. It has been taken into account that the performance gain pays off the downside. Sometimes performance could be improved in both ways, e.g. when garbage collection is performed less when unneccessary memory allocation is avoided, this also is positive for the execution performance.
The ANTLR based parser grammars have been refactored to perform better. Adding the location information was performed by subclass of the parser, which was now removed. The respective code has been inlined into the parsers.
The AST classes (*.internal.*.ast.*) usually maintain lists or arrays of other AST elements. When these collections are empty, the instance field will be assigned to a constant empty array or collection. This avoids the unneccessary instantiation and references to empty collections.
Class Identifier, which usually makes the largest part of the AST elements, has been refactored. The strings that make up identifiers are separated into segments, which are hold by the newly introduced datastructure QualifiedName. String segments are interned in a weak cache, as well as QualifiedName instances. It is assured that only one instance per string or QualifiedName will exist. The weak cache allows instances to be garbage collected once they are not referenced.
The overall memory consumption of the AST has been decreased by >50%.
The BuiltInMetaModel remembered cache misses for any queried type. This caused its cache map to grow and perform less. The BuiltInMetaModel will cache only type mappings for which it is responsible.
The usage of regular expressions for matching type names have been replaced by a faster implementation. (401144)
Xpand's builder performs now faster. Xpand searches the classpath for resources when queried by name. Therefore also jar archives are also searched. With Xpand 1.3 a blacklist is maintained to know which jar archives can be ignored in subsequent searches.
The feedback of the builder has been also improved. During a build, the progress monitor will now report detailed feedback on the current processing step and progress.
- Resource caching in ExecutionContextImpl fixed (329453)
- Added caching of results in TypesystemImpl (395727)
- Improved analysis for ambiguous extensions (401505)
The UML Typesystem adapter has been updated to support MDT UML2 Version 4.x.
- Sources for some plugins (e.g. org.eclipse.xtend.util.stdlib) were missing in the SDK (322980)
- Tests for XSD Typesystem have been integrated into the build
- «ENDREM-»: Xpand did not support the newline suppressing operator "-" for the ENDREM tag. Parser, Content Assist and Syntax Coloring have been fixed. (322394)
- Templates with same file name: In the syntax analysis an error was shown, when two templates have the same file name, but different definitions within. The template that invokes one of these definitions with «EXPAND» might have an error marker ("Couldn't find definition..."). (400105)
- Extensions from projects in development workspace: When extensions are used from plugin projects in a runtime test environment, the classpath folders from the plugins in development workspace are linked folders that contribute to the plugin classpath in the test environment. This is a quite typical scenario when developing and testing Xpand plugins. Using extensions from these plugin projects failed with exceptions and required to use a deployed version of the plugin, or importing these projects into the test workspace. (338695)
- XMLBeautifier: The XMLBeautifier escaped newline characters with
on Windows when using Mixed Content. The beautifier has been extended to configure the desired newline format (SYSTEM, UNIX, WINDOWS). For older Xpand versions it is possible to work around the issue by configuration. (356576, 400672)
Version 1.2.1 (Juno)
Xpand 1.2.1 is a maintnance release and was released with Eclipse Juno.
Bugzilla Report (33 issues resolved)
Version 1.1.0 (Indigo)
Xpand 1.1.0 is a maintnance release and was released with Eclipse Indigo.
- Bugzilla Report (37 issues resolved)
Version 1.0.0 (Helios)
Xpand 1.0.0 is the first graduated release at Eclipse and was released with Eclipse Helios.
- Bugzilla Report (142 issues resolved)
Xpand is now shipped with an optional incremental generation facility. This works very similar to the incremental Java compiler in Eclipse. It detects which parts of a model have changed since the last generation process. It then determines which files need to be generated due to that change and which are unaffected by it. Only the former are the regenerated, while the latter remain untouched.
Big models benefit from this feature. The generation of models with 1000 elements takes 50% of the time without incremental generation.
In large projects, generator speed is an issue, and the backend is designed with performance in mind. This requirement is what actually sparked its development in the first place. For performance and/or obfuscation reasons, the backend will serve as a basis for compilation into Java classes.
The design was driven by the following forces:
- Language independence
- Independent of parse tree
- Language interoperability
- Reuse of Tooling
Xpand provides profiler facilities by defining a profiling component. An example workflow using the profiler is shipped with the generator sample project (generatorWithProfiler.mwe).
A lot of enhancements are done for the Xpand editors.
- The navigation of the Xpand editors is improved by more specific navigation proposals
- Extension imports are now hyperlinks to the extension files
- The Xpand project wizard allows a more detailed project configuration
- A lot of other enchantments like markers for missing/not existing metamodels
- ONFILECLOSE: The ONFILECLOSE keyword is added to the EXPAND statement and allows a deferred evaluation of the EXPAND statement. The evaluation of the EXPAND statement is deferred until the FILE statement is closed.
- Java extensions: Since Xpand 0.8.0 non-static Java method can be called from Xtend.
Version 0.7.0 (Galileo)
The 0.7.0 version of the Xpand component from M2T is the first official Eclipse release of it. Xpand is a statically typed template language, featuring polymorphic dispatch, extensions and an open pluggable type system. It comes with Eclipse-based IDE support.
Xpand has previously been a part of openArchitectureWare and is used in many big projects and also shipped with some commercial products.
For the 0.7.0 release, the team has done some major performance improvements. Not only the runtime is up to 60% faster but due to aggressive caching we were able to improve the performance of the static analysis in the IDE about 400%.
As this is the first release at Eclipse, some of the UI-features are outlined here.
When you open Eclipse and import a project into the workspace you can see several file decorating images.
There are specific images for
- Xpand2 templates (.xpt extension)
- Extension files (.ext extension)
- Check constraints (.chk extension)
When you double-click on one of the above mentioned file types, special editors will open that provide appropriate syntax coloring. Syntax coloring
Here are examples for the Xpand editor:
for the Extensions editor:
and for Check editor:
The Editors provide extensive code completion support by pressing Ctrl + Space similar to what is known from the Java editor. Available types, properties, and operation, as well as extensions from .ext files will be found. The Xpand editor provides additionally support for the Xpand language statements. Xpand tag delimiter creation support.
In the Xpand editor there is an additional keystroke available to create the opening and closing tag brackets, the guillemets ("«" and "»").
Ctrl + < creates "«"
Ctrl + > creates "»"