-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Don't publish empty scala-library:%dotty-version% #9024
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
Labels
Comments
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 2, 2020
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 6, 2020
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 9, 2020
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 9, 2020
anatoliykmetyuk
added a commit
that referenced
this issue
Oct 12, 2020
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 13, 2020
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 14, 2020
anatoliykmetyuk
added a commit
to dotty-staging/dotty
that referenced
this issue
Oct 14, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently an empty jar is being published along the compiler which is called
scala-compiler:%dotty-version%
-scala-compiler:0.23
etc.The explanation is given that it is in order to make sure some tools don't break when working with Dotty. I believe this only hides the issues for those tools and might cause more issues in the long run.
For example when trying to work with Mill some users reported that the code doesn't compile with Bloop: scalameta/metals#1768
After some investigation it turned out there might be some logic in Zinc/Bloop that searches for scala-library and finds the empty jar instead of the actual
scala-library:2.13.1
. Without the additional jar, this would quickly come up and could be fixed inside Mill. Instead, we needed to spend more time on investigating this.I think it doesn't make sense anymore to publish it.
The text was updated successfully, but these errors were encountered: