Child pages
  • What's new in MPS 2.5 M1

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • MutliForEachStatement
  • others?

Build Language

Build language Language is an extensible build automation DSL for defining builds in a declarative way. Generated into Ant, it leverages Ant execution power while keeping your sources clean and free from minor detailsclutter. Organized as a stack of MPS languages with ANT at the bottom, it allows each part of your build procedure to be expressed at a different abstraction level. Building a complex artifact (like an MPS plug-in) could be specified in just one line of code, if you follow the language conventions, but, at the same time, nothing prevents you from diving into deeper and customize the details like file management or manifest properties.


Build script dependencies allow you to organize your build as a sequence of steps, ready to each of which may potentially run on a different machinesmachine. In At generation time, a sophisticated resolving resolution mechanism transforms the high-level dependencies into the appropriate ANT tasks. For example, a dependency on a java module is replaced with its compiled jar location. Referring to archives content implicitly extracts itand depending on the elements packaged inside existing archives will implicitly extracts them without any extra effort on your side.

Plug-ins packaging

Building Distributing languages for distribution as a plug-in ins for either IntelliJ IDEA, MPS or even as your own standalone IDE has become an extremely easy task. MPS-aware build language extension The functionality has been packaged into an extension to Build Language, which knows how to build MPS modules and supports all kinds of packaging. Build solution wizard helps to You can either write the whole script by hand or rely on the Build Solution Wizard, which helps you start with a new script.

New Scopes