-
Notifications
You must be signed in to change notification settings - Fork 71
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
Mill plugin (apparently) doesn't work on mill snapshot #1544
Comments
Dependencies to Mill itself should be specified with Also, depending on Mill |
Good points. I don't think anything prevents us from locking the dependency on 0.11.0. And the lack of % Provided scope is totally a mis-hap. @Quafadas, wanna have a go at PR-ing those changes ? Dependencies are defined here and used here : Lines 511 to 514 in f669528
|
What's the benefit of that over using the compile scope? I understand the point about pinning to the lowest version necessary, but this part I'm not sure about. |
It's to avoid to transitively bring in duplicate or incompatible Mill artifacts into the classpath. This is a somewhat historical recommendation, since when Mill was based on Ammonite, we couldn't fine-control the classpath plugins add. With newer Mill versions, this is a bit relaxed but still an issue. But I just recently tried to mitigate the issue completely (com-lihaoyi/mill#3189), but this will only apply to upcomming Mill versions greater equal |
I've published a teeny tiny repository here.
https://github.com/Quafadas/Smithy4sPluginCheck.git
It's pretty much a copy paste of the mill plugin docs.
With mill 0.11.7, I get success.
With mill 0.11.7-107-9ec9bc, I get this...
I noticed this in another project, where the error apparently manifests differently. I'm not clear if it's helpful to post that, as I think this is the "minimal" version.
On advice from discord, I also got out the class path.
https://discord.com/channels/632150470000902164/940067748103487558/1244294323873251460
mill --meta-level 1 show compileClasspath
In case it helps ...
There are some odd references, to mill 0.10.9? If that observation has any meaning here...
The text was updated successfully, but these errors were encountered: