-
-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ScalaPBModule always recompiles #4408
Comments
Did you change the dependencies between the runs? Technically, re-searching the deps should only necessary after a change. |
@nightscape Can you look into your |
@nightscape if you are on the latest version, would also be interesting to look at https://mill-build.org/mill/fundamentals/out-dir.html#_mill_invalidation_tree_json |
It looks like it's something entirely different, nothing to do with ScalaPB: mill -w server.compile and had VS Code + Metals running. ./mill -w server.compile everything works smooth and fast as expected. It's worth noting, that the two Mill processes seem to be aware of each other, at least the command-line Mill issued the following message:
Maybe it would be worth enhancing that message with a warning if the two Mill versions are not considered identical and invalidate each other's caches. |
You're most likely using two different JVMs. |
I have a Mill build using the ScalaPBModule. Everything is working correctly, but contrary to the way Mill usually efficiently caches results and only does the minimal amount of work, the Protobuf files are recompiled every time I make any changes to Scala code and compile.
Here's a simplified version of my
build.mill
:and here the relevant output of the Mill run after changing a Scala file:
I assume this has something to do with
because it's referring to my dependencies'
*.proto
files.The text was updated successfully, but these errors were encountered: