Clean deployment directory does not help, because build MDA is done without that.
Remove not used widgets is fine, when they are really big, but it keeps your project clean.
Check the userlib for evicted versions. I lot has been written about that for example https://forum.mendix.com/link/space/java%20actions/questions/101086
Further options:
Edit / Find Advanced / Unused items. But be careful, sometimes these are actually used in for example java-actions. So first exclude them, let the app run for a couple of weeks/months and then remove the excluded items. If you use the latest version of community commons, the ‘used by’ works for microflows, older one they are in the parameters as ‘MyModule.MyMicroflow’
Remove not used modules.
140 Mb is not evil, but smaller will deploy faster and keeping the project clean and tidy will reduce the chance on errors.
Thank you Chris and Eline for the tips!! Indeed I assumed that I needed to clean my project bit by bit, Remove not used parts etc. So gonna do that….
Hi Leon,
I don’t think this is a problematic size for an mda. That very much depends on the project. There are some reasons that can cause larger models:
regards, Fabian