I would say this is a windows problem rather than a maven problem. I have had similar problems trying to build simpler things where only solution is to reboot windows to unlock NTFS (NoT a File System).
I'm very seriously considering getting VMWare and installing a Linux Mint 20 and work in Linux instead. It seems like the only serious way to develop Java on a Windows 10 machine. Working on Windows directly costs to much time in constant reboots to resolve locks. I'm having a very good 4K display, which the free virtualbox does not support full size, thereby VmWare for me. If you don't have my display requirement, test with VirtualBox. Do note however that a virtual machine takes more memory! Personally I have 32 GB memory in my machine, but if you are at 16 GB or lower it can be problematic. And no, this wasn't exactly what you were asking. But since I'm having NTFS locks commonly even without multi threaded builds I don't believe the problem lies in maven. I have to admit that Windows 10 is far better than previous windows versions. It however seem to still be using same old, NTFS. Cheers, Tommy Från: Delany <delany.middle...@gmail.com> Svara: Maven Users List <users@maven.apache.org> Datum: 4 februari 2021 at 19:01:18 Till: Maven Users List <users@maven.apache.org> Ämne: exclusive execution scheduling We use the exec-maven-plugin (a thread-safe plugin) to call msbuild for dotnet builds within Maven. We have 8 dotnet projects with 3 of them depending on shared libraries in another directory in the repo (a total of 500 projects). With multi-threading on (4 threads), these dotnet projects always fail because the msbuild instances are all trying to lock the files in the shared libraries and can't open them in the other instances. This is on Windows 10 with NTFS. With only one thread, they always build successfully. Note that I don't use the multi-threading capabilities of msbuild because that would be silly. To get this reactor working I can either - package up the shared libraries as part of the build, and unpack them into every dotnet project that needs them (using https://maven.apache.org/plugins/maven-remote-resources-plugin/ ) Or ensure that no 2 instances of msbuild ever run at the same time, by either - chaining the dotnet projects together as one sequence of dependent projects (ridiculous) - building the dotnet projects separately with their own maven invocation - turning off multi-threading for the whole reactor Are there other options? Would it be feasible to consider adding a further thread-safe check in the plugin architecture whereby a configuration could be set to enforce that no two executions with the same id will ever run simultaneously? Thanks, Delany
