Skip to content

Accept OCL constraint files as build input and wire them into the generated VSUM project #36

Closed

Description

@uiysg

Context

POST /api/vsum/build and POST /api/vsum/jar (VsumController) only accept metamodelFiles, genmodelFiles and reactionFiles. VsumService.buildProject generates the project from its own templates and builds it with mvn clean verify.

Constraints are not considered anywhere, which is why they are missing from a VSUM built through the button in the Vitruvius Workbench(Methodologist-UI)

Tasks

  • VsumProjectBuildService.buildArtifact: write the files to `constraints/
  • VsumService.buildProject: copy the files to consistency/src/main/constraints/ and add their paths to VitruvConfiguration
  • Templates:
    • consistencyPom.ftl: add src/main/constraints as a resource directory
    • vsumPom.ftl: add tools.vitruv.dsls:vitruvocl-language only when constraints are present, with the version as a property
    • vsumExample.ftl: withConstraintChecker(VitruvOclConstraintChecker.fromClasspath(...)) for all constraint files
  • Ensure vitruvocl-language can be resolved in the Docker image / maven-repo volume

Activity

  1. self-assigned this
    on Oct 23, 2026
  2. linked a pull request that will close this issueBuild OCL constraints into generated VSUMs #51on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions