-
Notifications
You must be signed in to change notification settings - Fork 17
Publish the index to Maven Central again? #277
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
Comments
@alexarchambault any updates here? We need this to unblock com-lihaoyi/mill#3716 |
@lihaoyi The new indices are automatically published since #297 I have to cut a new release of coursier that includes coursier/coursier#3127 and coursier/coursier#3128, in order to allow using the new index. Will do it in the afternoon, Europe time, in order to get a few more PRs in. |
Fixed by #297 |
ok thanks! |
FYI, I'm having issues cutting a new coursier release. Publishing with Mill now requires Java >= 11. I'd like to keep supporting Java 8, so |
@alexarchambault you could use mill 0.11.12 if you want to use Java 8 i think, that should have gotten the publishign fix without the java version bump |
@lihaoyi That could have worked, yes. OTOH, it's nice to decouple the local JVM and the targeted one, so that we don't mistakenly bump the required JVM version. |
The index used to be published to Maven Central, see here.
It might be interesting to do that again, to work around GitHub outages.
See com-lihaoyi/mill#3716 for context
The text was updated successfully, but these errors were encountered: