You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Accept OCL constraint files as build input and wire them into the generated VSUM project #36
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