@micha your add-classpath suggestion seems to work out great. thank you, I wouldn't have found it on my own

awesome! it was a shot in the dark 🙂

@micha It was probably expected but sift doesn't play well with add-classpath (it doesn't notice files from the added path), so there I use set-env still, but this is OK, it's only for producing the final jar file

But now that I removed the watch + reload tasks altogether, maybe set-env is ok again to use. The problem was with reloading resources which caused the file errors on macOS