Skip to content

Releases: ContextMapper/context-mapper-dsl

v5.7.1

24 Feb 14:03
Compare
Choose a tag to compare

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

20 Feb 14:29
Compare
Choose a tag to compare

Changes in release v5.7.0:

  • Implemented mechanism to import other *.cml files into scope

    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 with D

v5.6.3

07 Feb 10:40
Compare
Choose a tag to compare

Release v5.6.3:

  • With this release we fixed the dependency problems for Eclipse 2019-12 (installation of Eclipse plugin).
  • We further changed our development environment including CI to work with Java 11 (Java 8 before).

v5.6.2

07 Feb 10:15
Compare
Choose a tag to compare

Release aiming to fix problems with plugin installation in Eclipse 2019-12 and change development environment (including CI) to Java 11. However, the release process was not Java 11 ready and failed.

Please install v5.6.3 instead!

v5.6.1

05 Dec 11:21
Compare
Choose a tag to compare

Bugfix release v5.6.1:

  • Fixed problem in MDSL generator:
    • multiple method parameters referencing empty domain objects (no attributes or references) no longer leads to exception
  • Service cut dialog: small UI improvements (layouting and labels)

v5.6.0

02 Dec 15:35
Compare
Choose a tag to compare

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:
    image
  • 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

23 Nov 09:40
Compare
Choose a tag to compare

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

21 Nov 18:33
Compare
Choose a tag to compare

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:

image

v5.4.1

19 Nov 17:07
Compare
Choose a tag to compare

Bugfix release v5.4.1:

  • Service cut generator: made dialog page for criteria priorities scrollable (may be necessary depending on screen resolution)
  • Service Cutter library: increased maximal amount of services to 62 (was 26)

v5.4.0

19 Nov 10:34
Compare
Choose a tag to compare

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