Releases: ContextMapper/context-mapper-dsl
Releases · ContextMapper/context-mapper-dsl
v5.7.1
Bugfix release v5.7.1:
- MDSL generator fixes:
- Update MAP pattern lists (responsibility patterns; see https://contextmapper.org/docs/mdsl/)
- Improve MDSL data type generation (no recursive trees; generate 'data type' for all CML types)
v5.7.0
Changes in release v5.7.0:
-
Implemented mechanism to import other *.cml files into scope
- Documented here: https://contextmapper.org/docs/imports/
- Example:
File-1.cml:
BoundedContext context1 BoundedContext context2
File-2.cml:
import "./File-1.cml" ContextMap { contains context1, context2 context1 -> context2 }
-
Updated MDSL generator to latest MDSL version.
V
has been replaced withD
v5.6.3
v5.6.2
v5.6.1
v5.6.0
Changes in release v5.6.0:
- CML language change: body and brackets ({ }) are now optional for all domain objects (entities, value objects, domain events, etc.), services, repositories etc. (tactic DDD objects)
- The domain vision statement is now supported on domains as well (not only subdomains).
- PlantUML generator: the references in the class diagram generator use the corresponding attribute names as labels now:
- MDSL generator bugfix: generator no longer throws an exception if entities without attributes are referenced (such entities are ignored for generating the parameter tree).
- Service cut generator: The dialog of the service cut generator has been improved (#156).
- New coupling criteria categories.
- Buttons which allow to prioritize all criteria of one category (see screenshot here).
- Service cut result CML: uses the name UnknownType instead of Nanoentity for the resulting attributes (#164; we currently do not know the original type of attributes, due to the current implementation of Service Cutter).
v5.5.1
Bugfix release v5.5.1:
- MDSL generator: do not use MDSL keywords as names for data types (cannot be compiled).
- Service cut generator: check that CML model contains some entities with attributes, otherwise no useful results can be calculated (precondition check).
v5.5.0
Changes in release v5.5.0:
- Improvements in the formatter for unparsing CML code (methods in domain objects such as entities, value objects etc.)
- Needed for generating CML models in our discovery library.
- Example of unparsed methods:
v5.4.1
v5.4.0
Changes and new features in v5.4.0:
- Generator context menu: adjusted order
- Graphical Context Map generator: changed dialog in Eclipse plugin so that multiple formats can be generated at once
- PlantUML generator: adjusted labels in component diagram for Customer-Supplier relationships (indicate which component is customer and which one is supplier)
- Integration of Service Cutter engine into Context Mapper:
- A new generator allows to create new Context Maps (CML files) on the basis of new service cuts suggested by the Service Cutter engine.
- Find documentation here