Skip to content

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

Closed
alexarchambault opened this issue Oct 11, 2024 · 7 comments · Fixed by #297
Closed

Publish the index to Maven Central again? #277

alexarchambault opened this issue Oct 11, 2024 · 7 comments · Fixed by #297

Comments

@alexarchambault
Copy link
Member

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

@lihaoyi
Copy link

lihaoyi commented Nov 3, 2024

@alexarchambault any updates here? We need this to unblock com-lihaoyi/mill#3716

@alexarchambault
Copy link
Member Author

@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.

@alexarchambault alexarchambault linked a pull request Nov 4, 2024 that will close this issue
@alexarchambault
Copy link
Member Author

Fixed by #297

@lihaoyi
Copy link

lihaoyi commented Nov 4, 2024

ok thanks!

@alexarchambault
Copy link
Member Author

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 --release 8 needs to be passed to scalac, but this breaks access to unsupported JDK APIs (sun.misc.{Signal, SignalHandler} here). Just stumbled upon scala/bug#13015 that has a workaround, I should be able to give it a try, but only in a few hours

@lihaoyi
Copy link

lihaoyi commented Nov 5, 2024

@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

@alexarchambault
Copy link
Member Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants