Tests failing due to outdated hot-deploy artifacts

Support
#1

During the migration process of an application based on Jmix 1.5.5 to 2.3.4 I faced an issue which did not resolve executing a clean-task.

I basically recreated the application and moved code into the new project as suggested. During this process and git move actions the package of migrated code changed.

Startup tests failed even after a clean rebuild while trying to load moved code. I wondered how the attempt could occur since the package does not exist at all anymore.

A search using IntelliJ Idea did not help finding. Using a full text search on the hard disk showed me, there were outdated compilation artifacts in the directory: .jmix/conf.

What is this good for and how to clean it properly?

#2

The .jmix/conf folder is used for hot deploy - the running application loads resources and classes from it in a priority.

You could safely remove this folder if you don’t use it yourself for something else.

Regards,
Konstantin

#3

@krivopustov I did in the meantime yes.

Hot deploy makes sense: It was enabled before I migrated packages and I re-enabled it now way after moving code. The startup tests now tried to load a bean which does not exist anymore.

Maybe the grade clean task should vanish the folder .jmix/conf as well?

#4

Maybe. We are going to sort it out in the next release, see Clean conf directory on application start · Issue #3451 · jmix-framework/jmix · GitHub