-
Notifications
You must be signed in to change notification settings - Fork 81
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
Error using Scala 3.2.0 and 3.2.1-RC2: package scala.compiletime does not have a member method summonFrom #702
Comments
Thanks for reporting! This should have been fixed by |
@tgodzik Let me try the latest. If it also does not work, I will set-up a project to reproduce this. |
I have run this with 2.3.3 and 2.3.4 and have the same results. I will create an example project. |
Actually, what do you use to run mdoc? It needs to be fixed there actually to bring in the newest Scala library and compiler. |
@tgodzik I have set up this project that uses Mill to start an MDoc process to compile the files Markdown files. I don know if you are familiar with Mill, so a quick rundown: The build script is in Here is an example of calling MDoc: user@node:~/VSCodeProjects/mdocMill$ ./mill -i tutorial.mdoc For this setup: val ScalaVersion = "3.2.1-RC2" // "3.2.1-RC2" "3.2.1-RC1" "3.2.0" "3.1.3"
def scalaMdocVersion = T("2.3.4") // "2.3.4" "2.3.3" "2.2.4" I get:
I get the same results for MDoc To facilitate debugging I can show the classpath used to call MDoc by un-commenting this line (just uncomment and run the mdoc target again). Below is the list of Jars used in the classpth to invoke MDoc. The version number seems to be ok. Can you confirm? List of jars used in classpath
|
It seems you should exclude the Scala version brought in by Mdoc and just use whichever is needed for the project. That's what is done in the sbt plugin and it works. Mdoc is built with 3.1.3 to be compatible for all the downstream versions, so the default dependency will be Scala 3.1.3, which can't read Scala 3.2.x |
I see. All scala-lang jars must use the project Scala version, not MDocs. Need to see how best to do this. Thank you. |
I have a similar problem when trying to add a dependency:
Where
I get the following error many times:
I suspect the problem is due to Without
Any idea how I could fix this? I tried setting the Scala version by adding |
Your cases seems to work correctly for me 🤔
You might need to exclude the Scala jars coming from mdoc so some options might be:
We could probably declare an app on coursier-apps for that with everything set up. Please let me know if any of the suggestions work, I will try to reproduce again |
Ok, this should work:
so basically adding --force-version org.scala-lang:scala3-compiler_3:3.2.2 Might be good to do mdoc3 app with that defined if anyone is interested |
Thanks, @tgodzik, using
(There is just a If I don't use |
I was using another shell, sorry 😓
Sure, we can add one paragraph about it, but probably it would be useful to have a separate app also. |
I am calling MDoc from a Mill script (forks a JVM).
I am using the latest
2.3.3
version of MDoc.If I use the Scala version
3.1.3
it works correctly.If I use Scala versions
3.2.0
or3.2.1-RC2
I get the error:A search shows that this issue has been encountered before here and here.
Could this be a publishing issue?
TIA
The text was updated successfully, but these errors were encountered: