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
The checks only run as part of /api/vsum/build and /api/vsum/jar. The platform needs to check the working copy after every auto-save: 5 seconds after the last change, at the latest every 60 seconds (vitruv-tools/Vitruv-UI-Methodologist#635). The problems are shown as warnings while users edit. That has to happen without generating a project, without running Maven, and without waiting behind a running build.
Proposal
POST /api/vsum/validate
Takes the same multipart input as /api/vsum/build.
Runs the same checks the build runs before Maven, through the same code.
Doesn't write a project to disk and doesn't run Maven.
Returns 200 with { valid, problems }, also for invalid projects. valid is false if there are any problems. Returns 400 only for malformed requests.
Doesn't use the build slots (max-concurrent-builds), so it never waits behind a running build.
Acceptance criteria
An invalid project returns 200 with valid: false and the same problems the build would report before Maven.
A validation request is answered while a build is running.
Activity