Environment
Jmix version: 3.0.0
Bug Description
The app-info.json, used by Studio to detect a running application is written to a fixed, process-agnostic path derived only from the project's conf directory.
As a result, every Jmix web application context started from the same project directory writes to - and, via a JVM shutdown hook, deletes - the very same file.
The most common trigger is the test suite: integration and UI tests (@SpringBootTest).
Steps to reproduce
- Start the application (bootRun) from a project directory; confirm
.jmix/conf/app-info/app-info.json exists.
- Keep the application running.
- From the same project directory, run the test task that boots a Spring/Jmix context.
- Observe
app-info.json after the tests finish.
Actual behavior
app-info.json is deleted.
Expected behavior
A running application's app-info.json should not be removed or overwritten by other JVM processes.
Environment
Jmix version: 3.0.0
Bug Description
The
app-info.json, used by Studio to detect a running application is written to a fixed, process-agnostic path derived only from the project's conf directory.As a result, every Jmix web application context started from the same project directory writes to - and, via a JVM shutdown hook, deletes - the very same file.
The most common trigger is the test suite: integration and UI tests (
@SpringBootTest).Steps to reproduce
.jmix/conf/app-info/app-info.jsonexists.app-info.jsonafter the tests finish.Actual behavior
app-info.jsonis deleted.Expected behavior
A running application's app-info.json should not be removed or overwritten by other JVM processes.